Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • R Rancher
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • barry cho
  • Rancher
  • Repository
Switch branch/tag
  • rancher
  • pkg
  • multiclustermanager
  • capabilities
  • http_request_body.go
Find file BlameHistoryPermalink
  • Michal Jura's avatar
    Refactor GKE proxy for UI calls · 5d9bfb2e
    Michal Jura authored Mar 18, 2021
    GKE Kontainer Engine v2 will use cloud credentials. For checking GKE
    cluster capabilities cloud credentials should be also used.
    GKE Kontainer Engine v1 should works as before.
    
    Example test HTTP call for testing cloud credentials
    
        ```
        $ curl -u $TOKEN "https://localhost:8443/meta/gkeSubnetworks?cloudCredentialId=cattle-global-data:cc-abcde&region=us-west1&zone=us-west1-a&projectId=my-project-id"
        ```
    5d9bfb2e

免费DevSecOps平台,让您的项目体验完整的DevSecOps流程,让项目更安全