UNCLASSIFIED - NO CUI

Skip to content
Snippets Groups Projects

Draft: Resolve "Provide tooling to migrate an active cluster from Operator Istio to Helm Istio."

Open Draft: Resolve "Provide tooling to migrate an active cluster from Operator Istio to Helm Istio."
2283-provide-tooling-to-migrate-an-active-cluster-from-operator-istio-to-helm-istio into master
3 unresolved threads
Open Greg M requested to merge 2283-provide-tooling-to-migrate-an-active-cluster-from-operator-istio-to-helm-istio into master
3 unresolved threads

See: #2283

Edited by Greg M

Merge request reports

Checking pipeline status.

Requires 2 approvals from eligible users and Code Owners.
Merge blocked: 3 checks failed

Merge details

  • The source branch is 58 commits behind the target branch.
  • 1 commit and 1 merge commit will be added to master (squashes 19 commits).
  • Source branch will be deleted.

  • Mentions issue #2283

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
docs/guides/using-bigbang/migrating-istio-in-bb3.0.md 0 → 100644
1 # Upgrading from the Istio Operator to Helm based Istio
  • Greg M added 1 commit

    added 1 commit

    • 3d40f6f3 - Edit migrating-istio-in-bb3.0.md

    Compare with previous version

  • Greg M added 1 commit

    added 1 commit

    • ae063ce0 - Edit migrating-istio-in-bb3.0.md

    Compare with previous version

  • Greg M added 1 commit

    added 1 commit

    • 57104cbe - Edit migrating-istio-in-bb3.0.md

    Compare with previous version

  • Greg M added 1 commit

    added 1 commit

    • 75e62beb - Edit migrating-istio-in-bb3.0.md

    Compare with previous version

  • Zach Callahan
    Zach Callahan @zcallahan started a thread on the diff
    • docs/guides/using-bigbang/migrating-istio-in-bb3.0.md 0 → 100644
    1 # Upgrading from the Istio Operator to Helm based Istio
    2
    3 ### *The new Istio Helm packages are BETA in Big Bang 2.x and will be stable in 3.0*
    4
    5 ### Step 1 : Remove Istio from your current deployment
    6 Before upgrading to the new Helm-based Istio packages, first disable the Istio and Istio's Operator packages:
    7 ```yaml
    8 istio:
    9 enabled: false
    10 istioOperator:
    11 enabled: false
    • Zach Callahan
      Zach Callahan @zcallahan ·
      Developer

      suggestion: there should be no reason the customer needs to disable the istioOperator until after the migration is complete. We can disable istio and enable istioCore in one helm upgrade cycle. The istiod torn down by removing istio will be replaced by the istiod created by istioCore, allowing workloads in the cluster to re-establish their XDS connections. Then we'd completely sidestep the need to delete the namespace.

      Edited by Zach Callahan
    • Greg M
      Greg M @kipten ·
      Author Developer

      Excellent suggestion. I will give that a go in my customer template deployment and see if that's an easier approach.

    • Please register or sign in to reply
  • Greg M added 1 commit

    added 1 commit

    • 4bd3adcb - Edit migrating-istio-in-bb3.0.md

    Compare with previous version

  • Zach Callahan
    Zach Callahan @zcallahan started a thread on the diff
    • docs/guides/using-bigbang/migrating-istio-in-bb3.0.md 0 → 100644
    10 istioOperator:
    11 enabled: false
    12 ```
    13 After a few minutes, all pods in both the `istio-system` and `istio-operator` namespaces will have terminated. However, due due to Istio's finalizer, the `istio-system` namespace will be stuck in the `terminating` state.
    14
    15 Force the deletion of this namespace:
    16 ```bash
    17 kubectl get ns istio-system -o json | jq '.spec.finalizers = []' | kubectl replace --raw "/api/v1/namespaces/istio-system/finalize" -f -
    18 ```
    19 Both Istio namespaces are now removed yet other remnants of Istio still linger in the cluster including custom resources. Remove them as they will be recreated via the helm deployment of Istio. The quickest way to do this is by using the [istioctl CLI tool](https://istio.io/latest/docs/ops/diagnostic-tools/istioctl/).
    20
    21 On macOS or Linux install it with:
    22 ```bash
    23 brew install istioctl
    24 ```
    25 To complete the removal of remaining Istio components, purge as per [Istio's documentation](https://istio.io/latest/docs/setup/install/istioctl/#uninstall-istio):
  • Greg M added 1 commit

    added 1 commit

    • 79575948 - Edit migrating-istio-in-bb3.0.md

    Compare with previous version

  • Greg M marked this merge request as draft

    marked this merge request as draft

  • Greg M removed review request for @kipten

    removed review request for @kipten

  • Greg M added statusblocked label and removed statusreview label

    added statusblocked label and removed statusreview label

  • Greg M
    Greg M @kipten ·
    Author Developer

    blocked pending beta status change

    • Please register or sign in to reply

    UNCLASSIFIED - NO CUI