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
flux is not bootstrapping the OCM controllers as written in https://github.com/open-component-model/ocm-examples/tree/main/kubernetes/podify-walkthrough.
lux bootstrap github --owner ${GITHUB_USER} --repository ocm-example-podify-walkthrough --personal --path=./clusters ► connecting to github.com ► cloning branch "main" from Git repository "https://github.com/sTb1337/ocm-example-podify-walkthrough.git" ✔ cloned repository ► generating component manifests ✔ generated component manifests ✔ component manifests are up to date ✔ reconciled components ► determining if source secret "flux-system/flux-system" exists ✔ source secret up to date ► generating sync manifests ✔ generated sync manifests ✔ sync manifests are up to date ► applying sync manifests ✔ reconciled sync configuration ◎ waiting for GitRepository "flux-system/flux-system" to be reconciled ✔ GitRepository reconciled successfully ◎ waiting for Kustomization "flux-system/flux-system" to be reconciled ✔ Kustomization reconciled successfully ► confirming components are healthy ✔ helm-controller: deployment ready ✔ kustomize-controller: deployment ready ✔ notification-controller: deployment ready ✔ source-controller: deployment ready ✔ all components are healthy kubectl get deploy -n ocm-system No resources found in ocm-system namespace.
this is done after manually applying platform/ocm manifests
platform/ocm
k apply -f ocm_controller.yaml -f unpacker_controller.yaml customresourcedefinition.apiextensions.k8s.io/componentdescriptors.delivery.ocm.software configured customresourcedefinition.apiextensions.k8s.io/componentversions.delivery.ocm.software configured customresourcedefinition.apiextensions.k8s.io/configurations.delivery.ocm.software configured customresourcedefinition.apiextensions.k8s.io/localizations.delivery.ocm.software configured customresourcedefinition.apiextensions.k8s.io/resources.delivery.ocm.software configured customresourcedefinition.apiextensions.k8s.io/snapshots.delivery.ocm.software created serviceaccount/ocm-controller created role.rbac.authorization.k8s.io/leader-election-role created clusterrole.rbac.authorization.k8s.io/ocm-controller-manager-role created rolebinding.rbac.authorization.k8s.io/ocm-leader-election-rolebinding created clusterrolebinding.rbac.authorization.k8s.io/ocm-controller-rolebinding created deployment.apps/ocm-controller created customresourcedefinition.apiextensions.k8s.io/unpackers.delivery.ocm.software configured serviceaccount/unpacker-controller unchanged role.rbac.authorization.k8s.io/unpacker-leader-election-role unchanged clusterrole.rbac.authorization.k8s.io/unpacker-manager-role configured rolebinding.rbac.authorization.k8s.io/unpacker-leader-election-rolebinding unchanged clusterrolebinding.rbac.authorization.k8s.io/unpacker-rolebinding unchanged deployment.apps/unpacker-controller unchanged kubectl get deploy -n ocm-system NAME READY UP-TO-DATE AVAILABLE AGE ocm-controller 0/1 1 0 61s registry 1/1 1 1 58s unpacker-controller 1/1 1 1 2m6s
Is this manual step missing in documentation or did i do something wrong?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
flux is not bootstrapping the OCM controllers as written in https://github.com/open-component-model/ocm-examples/tree/main/kubernetes/podify-walkthrough.
this is done after manually applying
platform/ocm
manifestsIs this manual step missing in documentation or did i do something wrong?
The text was updated successfully, but these errors were encountered: