-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add initial vcluster support #22
Conversation
400cd56
to
abe2449
Compare
8bc4057
to
7820a58
Compare
7820a58
to
2bbb9f2
Compare
2b5ff22
to
1cd1dc9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some changes from my side, also
deployment.apps/cert-manager condition met
kubectl -n cert-manager wait --for condition=Available deployment/cert-manager-webhook --timeout 120s
deployment.apps/cert-manager-webhook condition met
make[1]: Leaving directory '/home/wejdross/vshn/shedar/kindev'
13:54:29 fatal current selected context "" is not a virtual cluster context. If you've used a custom context name you will need to switch manually using kubectl
make: *** [Makefile:88: /home/wejdross/vshn/shedar/kindev/.kind/certmanager-sentinel] Error 1
setup using command: make vshnall -e vcluster=true
fails
This will help with developing for splitted clusters, where crossplane and the services are not on the same clusters.
145f3b0
to
5dd1ea5
Compare
The problem was with an incompatible helm release. wejdross: Helm was OK, vcluster version checker was problematic :D |
This will help with developing for splitted clusters, where crossplane and the services are not on the same clusters.