Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-22195

Improve the GKE pipe to support private clusters (accessed through a bastion)

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • Pipelines - Pipes
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      The pipe for GKE (https://bitbucket.org/product/features/pipelines/integrations?p=atlassian/google-gke-kubectl-run) works well on public clusters, but not on private ones.

      For private GKE clusters, you need to first open an SSH tunnel through a bastion, and then use it as an HTTPS proxy for kubectl (see https://cloud.google.com/kubernetes-engine/docs/tutorials/private-cluster-bastion)

      It's certainly possible to do that manually with a script.

      But it would be way better if your built-in pipe supported it.

      NB: original question was https://community.atlassian.com/t5/Bitbucket-questions/Could-the-GKE-pipe-be-improved-to-support-private-clusters/qaq-p/2158869

      Attachments

        Activity

          People

            Unassigned Unassigned
            33bde36bcd1d Mossroy
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: