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

Use new templates for cilium 1.8 #9424

Merged
merged 3 commits into from
Jul 3, 2020

Conversation

olemarkus
Copy link
Member

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)

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. area/addons labels Jun 22, 2020
@olemarkus olemarkus force-pushed the cilium-1.18 branch 4 times, most recently from 35d1ec0 to fc03eb9 Compare June 24, 2020 17:44
@olemarkus olemarkus changed the title WIP: Use new templates for cilium 1.8 Use new templates for cilium 1.8 Jun 24, 2020
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 24, 2020
@olemarkus
Copy link
Member Author

/assign @rifelpet

@@ -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"
Copy link
Member

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.

Copy link
Member Author

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
Copy link
Member

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.

Copy link
Member Author

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
Copy link
Member

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?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep. That makes sense.

Copy link
Member Author

@olemarkus olemarkus left a 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
Copy link
Member Author

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.

@@ -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"
Copy link
Member Author

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
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep. That makes sense.

@olemarkus
Copy link
Member Author

/retest

@k8s-ci-robot k8s-ci-robot added the area/provider/spotinst Issues or PRs related to spotinst provider label Jun 29, 2020
@hakman
Copy link
Member

hakman commented Jun 29, 2020

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 29, 2020
@olemarkus
Copy link
Member Author

Hm. Nodeup is slower than usual.

/retest

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 30, 2020
@olemarkus
Copy link
Member Author

/retest

@olemarkus
Copy link
Member Author

/retest

1 similar comment
@olemarkus
Copy link
Member Author

/retest

@hakman
Copy link
Member

hakman commented Jun 30, 2020

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 30, 2020
@hakman
Copy link
Member

hakman commented Jul 2, 2020

@johngmyers any other thoughts here, or it's good from your point of view also?

@johngmyers
Copy link
Member

Good from my point of view.

@rifelpet
Copy link
Member

rifelpet commented Jul 2, 2020

/approve

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 2, 2020
@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

1 similar comment
@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

@rifelpet
Copy link
Member

rifelpet commented Jul 3, 2020

/lgtm cancel

might need a rebase + hack/update-* scripts to fix the failing jobs

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 3, 2020
@hakman
Copy link
Member

hakman commented Jul 3, 2020

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 3, 2020
@k8s-ci-robot k8s-ci-robot merged commit f33a5e7 into kubernetes:master Jul 3, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.19 milestone Jul 3, 2020
@olemarkus olemarkus deleted the cilium-1.18 branch July 7, 2020 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/addons area/api area/provider/spotinst Issues or PRs related to spotinst provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants