cluster-api-provider-azure icon indicating copy to clipboard operation
cluster-api-provider-azure copied to clipboard

WIP ci: use helm to install calico CNI

Open jackfrancis opened this issue 3 years ago • 12 comments

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This PR replaces the exising ClusterResourceSet-dependent solution for automating calico CNI delivery onto test clusters (and reference cluster templates) with a helm solution. For the private cluster scenario, we're keeping the CRS-dependent solution as a practical way to install the CNI from the management cluster (we have no direct access to the apiserver to helm install gestures and we don't yet have a E2E solution to indirectly access the apiserver in such scenarios).

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged): Fixes #2063 Contributes to #2179

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

  • [ ] squashed commits
  • [ ] includes documentation
  • [ ] adds unit tests

Release note:

remove calico ClusterResourceSets from reference cluster templates

jackfrancis avatar May 26 '22 20:05 jackfrancis

/test pull-cluster-api-provider-azure-e2e-optional

jackfrancis avatar May 27 '22 21:05 jackfrancis

Is this PR going to support installing calico on Windows cluster and fix the issue? https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/2341

lzhecheng avatar Jun 01 '22 23:06 lzhecheng

@lzhecheng Yes, definitely we will ensure that the installed calico helm chart has support for all Windows scenarios.

jackfrancis avatar Jun 02 '22 16:06 jackfrancis

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please ask for approval from jackfrancis after the PR has been reviewed.

The full list of commands accepted by this bot can be found 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 avatar Jun 07 '22 20:06 k8s-ci-robot

/test pull-cluster-api-provider-azure-e2e-optional

jackfrancis avatar Jun 07 '22 22:06 jackfrancis

/retest

jackfrancis avatar Jun 08 '22 22:06 jackfrancis

/retest

jackfrancis avatar Jun 09 '22 21:06 jackfrancis

/test pull-cluster-api-provider-azure-e2e-optional

jackfrancis avatar Jun 10 '22 00:06 jackfrancis

/test pull-cluster-api-provider-azure-e2e-optional

jackfrancis avatar Jun 10 '22 21:06 jackfrancis

@jackfrancis: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-cluster-api-provider-azure-e2e-optional b9f124442718f20c8be763cc8602513baa94006d link false /test pull-cluster-api-provider-azure-e2e-optional

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

k8s-ci-robot avatar Jun 10 '22 21:06 k8s-ci-robot

@jackfrancis: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Jun 25 '22 00:06 k8s-ci-robot

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Sep 23 '22 01:09 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Oct 23 '22 02:10 k8s-triage-robot

/close

CecileRobertMichon avatar Nov 02 '22 18:11 CecileRobertMichon

@CecileRobertMichon: Closed this PR.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Nov 02 '22 18:11 k8s-ci-robot