-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
update calico policy controller to 1.0.0 #3791
Comments
We need to upgrade it, pretty simple if you would like to contribute |
Which version of kops btw? |
I am running kops 1.7, but deploying a 1.8 k8s cluster. Happy to contribute, do you think is as easy as swapping the current template with the new calico recommended template? https://docs.projectcalico.org/v2.6/getting-started/kubernetes/installation/hosted/kubeadm/1.6/calico.yaml plus/minus adjustments |
Here is an example of a manifest for 1.8 6d624c7#diff-fba0e0542d346bfcca2d1553d1a48b0d Add new manifest, and update boostrapper Please use the manifest from the calico repo. We should have rbac rules in the 1.7 manifest |
Automatic merge from submit-queue. Update calico template closes #3791 changes taken from https://docs.projectcalico.org/v2.6/getting-started/kubernetes/installation/hosted/hosted just a POC. not sure if I should update the 1.6 template or create a new template for 1.8 (maybe 1.7?) as I did. Do you have any suggestions on how to test this?
Out of the box, the calico networking is set up with the policy controller 0.7.0 that doesn't support k8s 1.8 network policy definitions. Is this on the roadmap, and is it as easy as just bumping the image version on the template?
The text was updated successfully, but these errors were encountered: