-
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
Use new templates for cilium 1.8 #9424
Conversation
35d1ec0
to
fc03eb9
Compare
/assign @rifelpet |
pkg/model/components/cilium.go
Outdated
@@ -39,7 +40,7 @@ func (b *CiliumOptionsBuilder) BuildOptions(o interface{}) error { | |||
if b.Context.IsKubernetesLT("1.12.0") { | |||
c.Version = "v1.6.9" | |||
} else { | |||
c.Version = "v1.7.4" | |||
c.Version = "v1.8.0-rc4" |
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.
Shouldn't we default to a release version?
I'm wondering if we would want k8s 1.17 and earlier to stay on 1.7.
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.
We should now that 1.8.0 is actually released. Will fix.
Normally we don't do this with CNIs unless there are manifest incompatibilities, but the code changes I've made makes this an option. I am neutral on this.
CiliumPrometheusPort = 9090 | ||
|
||
// CiliumHubblePrometheusPort is the default port where Hubble exposes metrics | ||
CiliumHubblePrometheusPort = 9091 |
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.
Are these host network? I think we want wellknownports (or at least something) to track the host-network ports.
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.
Yep. These ports are exposed on the CNI agent itself.
- id: k8s-1.12 | ||
kubernetesVersion: '>=1.12.0' | ||
manifest: networking.cilium.io/k8s-1.12.yaml | ||
manifestHash: 61f05c6e376a570b3f1e53d6b0b2ed9e63cf4c50 | ||
manifest: networking.cilium.io/k8s-1.12-v1.8.yaml |
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.
Perhaps add a test for configuring Cilium to 1.7?
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.
Yep. That makes sense.
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.
Thanks for spotting my silly mistakes.
CiliumPrometheusPort = 9090 | ||
|
||
// CiliumHubblePrometheusPort is the default port where Hubble exposes metrics | ||
CiliumHubblePrometheusPort = 9091 |
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.
Yep. These ports are exposed on the CNI agent itself.
pkg/model/components/cilium.go
Outdated
@@ -39,7 +40,7 @@ func (b *CiliumOptionsBuilder) BuildOptions(o interface{}) error { | |||
if b.Context.IsKubernetesLT("1.12.0") { | |||
c.Version = "v1.6.9" | |||
} else { | |||
c.Version = "v1.7.4" | |||
c.Version = "v1.8.0-rc4" |
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.
We should now that 1.8.0 is actually released. Will fix.
Normally we don't do this with CNIs unless there are manifest incompatibilities, but the code changes I've made makes this an option. I am neutral on this.
- id: k8s-1.12 | ||
kubernetesVersion: '>=1.12.0' | ||
manifest: networking.cilium.io/k8s-1.12.yaml | ||
manifestHash: 61f05c6e376a570b3f1e53d6b0b2ed9e63cf4c50 | ||
manifest: networking.cilium.io/k8s-1.12-v1.8.yaml |
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.
Yep. That makes sense.
/retest |
/lgtm |
Hm. Nodeup is slower than usual. /retest |
/retest |
/retest |
1 similar comment
/retest |
/lgtm |
@johngmyers any other thoughts here, or it's good from your point of view also? |
Good from my point of view. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus, rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
/lgtm cancel might need a rebase + hack/update-* scripts to fix the failing jobs |
/lgtm |
WIP at least until cilium 1.8 has been released.
Using a new template here since cilium templates have changed quite a bit for 1.8.
Also adding support for hubble. Right now, it is just possible to enable it. But need to add support for metrics at least. Not 100% decided if hubble-relay should be part of the addon or not. Possibly leave it to the user to install relay (and ui)