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.

Sign up for GitHub

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

Jump to bottom

[v14] Prevent double registration of Kubernetes GVK for older Kube clusters #33402

Merged
merged 2 commits into from Oct 13, 2023
Merged

[v14] Prevent double registration of Kubernetes GVK for older Kube clusters #33402

merged 2 commits into from Oct 13, 2023

Commits on Oct 12, 2023

  1. Prevent double registration of Kubernetes GVK for older Kube clusters 

    Older Kubernetes clusters might have types that live outside of default
Kubernetes types but are registered using different APIs. When Teleport
starts, it tries to pull the resources from the cluster and panics
because a certain type is already registered.

This PR adds a check that prevents double registration.

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
    @tigrato
    tigrato authored and github-actions committed Oct 12, 2023
    Configuration menu
    Copy the full SHA
    b09b589 View commit details
    Browse the repository at this point in the history

  2. add unit test to check for panic

    @tigrato
    tigrato authored and github-actions committed Oct 12, 2023
    Configuration menu
    Copy the full SHA
    eb23991 View commit details
    Browse the repository at this point in the history