We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
$ clusteradm init --feature-gates=DefaultClusterSet=false $ kc get clustermanager cluster-manager -oyaml apiVersion: operator.open-cluster-management.io/v1 kind: ClusterManager metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: "" creationTimestamp: "2024-11-11T05:02:44Z" finalizers: - operator.open-cluster-management.io/cluster-manager-cleanup generation: 1 name: cluster-manager resourceVersion: "3127" uid: 22497245-8d7c-4c22-baaa-103b3af6df6b spec: addOnManagerConfiguration: featureGates: - feature: AddonManagement mode: Enable addOnManagerImagePullSpec: quay.io/open-cluster-management/addon-manager:v0.15.0 deployOption: mode: Default placementImagePullSpec: quay.io/open-cluster-management/placement:v0.15.0 registrationConfiguration: autoApproveUsers: - system:serviceaccount:open-cluster-management:cluster-bootstrap featureGates: - feature: DefaultClusterSet mode: Enable registrationImagePullSpec: quay.io/open-cluster-management/registration:v0.15.0 resourceRequirement: type: Default workConfiguration: workDriver: kube workImagePullSpec: quay.io/open-cluster-management/work:v0.15.0
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Environment ie: OCM version, clusteradm version, Kubernetes version and provider:
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
api
DefaultClusterSet
@RokibulHasan7 did you try the latest build, I think this was fixed by #456
Sorry, something went wrong.
yes, tried with the latest build.
Successfully merging a pull request may close this issue.
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Environment ie: OCM version, clusteradm version, Kubernetes version and provider:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: