Skip to content
New issue

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

OSM is in crashbackoff loop #6

Closed
briandenicola opened this issue Oct 31, 2021 · 3 comments
Closed

OSM is in crashbackoff loop #6

briandenicola opened this issue Oct 31, 2021 · 3 comments

Comments

@briandenicola
Copy link
Owner

No description provided.

@briandenicola
Copy link
Owner Author

CRD for Service Mesh Interface are missing. Might be due to firewall rule.

Added firewall route for - openservicemesh.github.io
Installed via Helm - helm upgrade -i osm osm --repo https://openservicemesh.github.io/osm --version 0.11 --namespace kube-system and it worked

0.11 is the supported version for 1.22

The helm command created the required CRDs. and after this the add-on command also work.

Still need to test on a clean cluster

@briandenicola
Copy link
Owner Author

My guess is the firewall rule is the reason it works now. The helm chart doesn't define any CRDs directly but looks to pull in a container that creates them - image: "openservicemesh/osm-crds@sha256:a211f9fb78ea058adcd73cfa7330865f8a1bc314fc1c9c2658e5f3b348dc033e

but the chart would have to be pull first

@briandenicola
Copy link
Owner Author

Moved to deploying OSM via Helm. Could not get OSM to deploy correctly in a private cluster with Azure firewall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant