2020-09-16 14:19:51 +00:00
|
|
|
// Copyright 2020 the Pinniped contributors. All Rights Reserved.
|
|
|
|
// SPDX-License-Identifier: Apache-2.0
|
2020-08-07 21:49:04 +00:00
|
|
|
|
2020-08-09 17:04:05 +00:00
|
|
|
package controllermanager
|
2020-08-07 21:49:04 +00:00
|
|
|
|
|
|
|
import (
|
|
|
|
"context"
|
|
|
|
"fmt"
|
|
|
|
"time"
|
|
|
|
|
|
|
|
"k8s.io/apimachinery/pkg/runtime"
|
|
|
|
k8sinformers "k8s.io/client-go/informers"
|
|
|
|
"k8s.io/client-go/kubernetes"
|
|
|
|
restclient "k8s.io/client-go/rest"
|
2020-09-14 15:47:16 +00:00
|
|
|
"k8s.io/klog/v2/klogr"
|
2020-08-09 17:04:05 +00:00
|
|
|
aggregatorclient "k8s.io/kube-aggregator/pkg/client/clientset_generated/clientset"
|
2020-08-07 21:49:04 +00:00
|
|
|
|
2020-09-18 19:56:24 +00:00
|
|
|
loginv1alpha1 "go.pinniped.dev/generated/1.19/apis/login/v1alpha1"
|
|
|
|
pinnipedclientset "go.pinniped.dev/generated/1.19/client/clientset/versioned"
|
|
|
|
pinnipedinformers "go.pinniped.dev/generated/1.19/client/informers/externalversions"
|
|
|
|
"go.pinniped.dev/internal/controller/apicerts"
|
|
|
|
"go.pinniped.dev/internal/controller/identityprovider/idpcache"
|
|
|
|
"go.pinniped.dev/internal/controller/identityprovider/webhookcachecleaner"
|
|
|
|
"go.pinniped.dev/internal/controller/identityprovider/webhookcachefiller"
|
|
|
|
"go.pinniped.dev/internal/controller/issuerconfig"
|
|
|
|
"go.pinniped.dev/internal/controllerlib"
|
|
|
|
"go.pinniped.dev/internal/provider"
|
2020-09-18 23:39:58 +00:00
|
|
|
"go.pinniped.dev/pkg/config/api"
|
2020-08-07 21:49:04 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
const (
|
|
|
|
singletonWorker = 1
|
|
|
|
defaultResyncInterval = 3 * time.Minute
|
|
|
|
)
|
|
|
|
|
|
|
|
// Prepare the controllers and their informers and return a function that will start them when called.
|
|
|
|
func PrepareControllers(
|
|
|
|
serverInstallationNamespace string,
|
Rename many of resources that are created in Kubernetes by Pinniped
New resource naming conventions:
- Do not repeat the Kind in the name,
e.g. do not call it foo-cluster-role-binding, just call it foo
- Names will generally start with a prefix to identify our component,
so when a user lists all objects of that kind, they can tell to which
component it is related,
e.g. `kubectl get configmaps` would list one named "pinniped-config"
- It should be possible for an operator to make the word "pinniped"
mostly disappear if they choose, by specifying the app_name in
values.yaml, to the extent that is practical (but not from APIService
names because those are hardcoded in golang)
- Each role/clusterrole and its corresponding binding have the same name
- Pinniped resource names that must be known by the server golang code
are passed to the code at run time via ConfigMap, rather than
hardcoded in the golang code. This also allows them to be prepended
with the app_name from values.yaml while creating the ConfigMap.
- Since the CLI `get-kubeconfig` command cannot guess the name of the
CredentialIssuerConfig resource in advance anymore, it lists all
CredentialIssuerConfig in the app's namespace and returns an error
if there is not exactly one found, and then uses that one regardless
of its name
2020-09-18 22:56:50 +00:00
|
|
|
namesConfig api.NamesConfigSpec,
|
2020-08-07 21:49:04 +00:00
|
|
|
discoveryURLOverride *string,
|
2020-08-11 01:53:53 +00:00
|
|
|
dynamicCertProvider provider.DynamicTLSServingCertProvider,
|
2020-08-20 19:17:18 +00:00
|
|
|
servingCertDuration time.Duration,
|
|
|
|
servingCertRenewBefore time.Duration,
|
2020-09-14 15:47:16 +00:00
|
|
|
idpCache *idpcache.Cache,
|
2020-08-07 21:49:04 +00:00
|
|
|
) (func(ctx context.Context), error) {
|
|
|
|
// Create k8s clients.
|
2020-08-20 17:54:15 +00:00
|
|
|
k8sClient, aggregatorClient, pinnipedClient, err := createClients()
|
2020-08-07 21:49:04 +00:00
|
|
|
if err != nil {
|
|
|
|
return nil, fmt.Errorf("could not create clients for the controllers: %w", err)
|
|
|
|
}
|
|
|
|
|
2020-08-09 17:04:05 +00:00
|
|
|
// Create informers. Don't forget to make sure they get started in the function returned below.
|
2020-08-20 17:54:15 +00:00
|
|
|
kubePublicNamespaceK8sInformers, installationNamespaceK8sInformers, installationNamespacePinnipedInformers :=
|
|
|
|
createInformers(serverInstallationNamespace, k8sClient, pinnipedClient)
|
2020-08-07 21:49:04 +00:00
|
|
|
|
|
|
|
// Create controller manager.
|
2020-08-28 15:59:09 +00:00
|
|
|
controllerManager := controllerlib.
|
2020-08-07 21:49:04 +00:00
|
|
|
NewManager().
|
|
|
|
WithController(
|
Rename many of resources that are created in Kubernetes by Pinniped
New resource naming conventions:
- Do not repeat the Kind in the name,
e.g. do not call it foo-cluster-role-binding, just call it foo
- Names will generally start with a prefix to identify our component,
so when a user lists all objects of that kind, they can tell to which
component it is related,
e.g. `kubectl get configmaps` would list one named "pinniped-config"
- It should be possible for an operator to make the word "pinniped"
mostly disappear if they choose, by specifying the app_name in
values.yaml, to the extent that is practical (but not from APIService
names because those are hardcoded in golang)
- Each role/clusterrole and its corresponding binding have the same name
- Pinniped resource names that must be known by the server golang code
are passed to the code at run time via ConfigMap, rather than
hardcoded in the golang code. This also allows them to be prepended
with the app_name from values.yaml while creating the ConfigMap.
- Since the CLI `get-kubeconfig` command cannot guess the name of the
CredentialIssuerConfig resource in advance anymore, it lists all
CredentialIssuerConfig in the app's namespace and returns an error
if there is not exactly one found, and then uses that one regardless
of its name
2020-09-18 22:56:50 +00:00
|
|
|
issuerconfig.NewPublisherController(serverInstallationNamespace,
|
|
|
|
namesConfig.CredentialIssuerConfig,
|
2020-08-07 21:49:04 +00:00
|
|
|
discoveryURLOverride,
|
2020-08-20 17:54:15 +00:00
|
|
|
pinnipedClient,
|
2020-08-09 17:04:05 +00:00
|
|
|
kubePublicNamespaceK8sInformers.Core().V1().ConfigMaps(),
|
2020-09-18 21:38:45 +00:00
|
|
|
installationNamespacePinnipedInformers.Config().V1alpha1().CredentialIssuerConfigs(),
|
2020-08-28 15:59:09 +00:00
|
|
|
controllerlib.WithInformer,
|
2020-08-09 17:04:05 +00:00
|
|
|
),
|
|
|
|
singletonWorker,
|
|
|
|
).
|
|
|
|
WithController(
|
|
|
|
apicerts.NewCertsManagerController(
|
|
|
|
serverInstallationNamespace,
|
Rename many of resources that are created in Kubernetes by Pinniped
New resource naming conventions:
- Do not repeat the Kind in the name,
e.g. do not call it foo-cluster-role-binding, just call it foo
- Names will generally start with a prefix to identify our component,
so when a user lists all objects of that kind, they can tell to which
component it is related,
e.g. `kubectl get configmaps` would list one named "pinniped-config"
- It should be possible for an operator to make the word "pinniped"
mostly disappear if they choose, by specifying the app_name in
values.yaml, to the extent that is practical (but not from APIService
names because those are hardcoded in golang)
- Each role/clusterrole and its corresponding binding have the same name
- Pinniped resource names that must be known by the server golang code
are passed to the code at run time via ConfigMap, rather than
hardcoded in the golang code. This also allows them to be prepended
with the app_name from values.yaml while creating the ConfigMap.
- Since the CLI `get-kubeconfig` command cannot guess the name of the
CredentialIssuerConfig resource in advance anymore, it lists all
CredentialIssuerConfig in the app's namespace and returns an error
if there is not exactly one found, and then uses that one regardless
of its name
2020-09-18 22:56:50 +00:00
|
|
|
namesConfig.ServingCertificateSecret,
|
2020-08-09 17:04:05 +00:00
|
|
|
k8sClient,
|
|
|
|
installationNamespaceK8sInformers.Core().V1().Secrets(),
|
2020-08-28 15:59:09 +00:00
|
|
|
controllerlib.WithInformer,
|
|
|
|
controllerlib.WithInitialEvent,
|
2020-08-20 19:17:18 +00:00
|
|
|
servingCertDuration,
|
2020-09-08 23:36:49 +00:00
|
|
|
"Pinniped CA",
|
Rename many of resources that are created in Kubernetes by Pinniped
New resource naming conventions:
- Do not repeat the Kind in the name,
e.g. do not call it foo-cluster-role-binding, just call it foo
- Names will generally start with a prefix to identify our component,
so when a user lists all objects of that kind, they can tell to which
component it is related,
e.g. `kubectl get configmaps` would list one named "pinniped-config"
- It should be possible for an operator to make the word "pinniped"
mostly disappear if they choose, by specifying the app_name in
values.yaml, to the extent that is practical (but not from APIService
names because those are hardcoded in golang)
- Each role/clusterrole and its corresponding binding have the same name
- Pinniped resource names that must be known by the server golang code
are passed to the code at run time via ConfigMap, rather than
hardcoded in the golang code. This also allows them to be prepended
with the app_name from values.yaml while creating the ConfigMap.
- Since the CLI `get-kubeconfig` command cannot guess the name of the
CredentialIssuerConfig resource in advance anymore, it lists all
CredentialIssuerConfig in the app's namespace and returns an error
if there is not exactly one found, and then uses that one regardless
of its name
2020-09-18 22:56:50 +00:00
|
|
|
namesConfig.APIService,
|
2020-09-08 23:36:49 +00:00
|
|
|
),
|
|
|
|
singletonWorker,
|
|
|
|
).
|
2020-09-16 20:00:03 +00:00
|
|
|
WithController(
|
|
|
|
apicerts.NewAPIServiceUpdaterController(
|
|
|
|
serverInstallationNamespace,
|
Rename many of resources that are created in Kubernetes by Pinniped
New resource naming conventions:
- Do not repeat the Kind in the name,
e.g. do not call it foo-cluster-role-binding, just call it foo
- Names will generally start with a prefix to identify our component,
so when a user lists all objects of that kind, they can tell to which
component it is related,
e.g. `kubectl get configmaps` would list one named "pinniped-config"
- It should be possible for an operator to make the word "pinniped"
mostly disappear if they choose, by specifying the app_name in
values.yaml, to the extent that is practical (but not from APIService
names because those are hardcoded in golang)
- Each role/clusterrole and its corresponding binding have the same name
- Pinniped resource names that must be known by the server golang code
are passed to the code at run time via ConfigMap, rather than
hardcoded in the golang code. This also allows them to be prepended
with the app_name from values.yaml while creating the ConfigMap.
- Since the CLI `get-kubeconfig` command cannot guess the name of the
CredentialIssuerConfig resource in advance anymore, it lists all
CredentialIssuerConfig in the app's namespace and returns an error
if there is not exactly one found, and then uses that one regardless
of its name
2020-09-18 22:56:50 +00:00
|
|
|
namesConfig.ServingCertificateSecret,
|
2020-09-16 20:00:03 +00:00
|
|
|
loginv1alpha1.SchemeGroupVersion.Version+"."+loginv1alpha1.GroupName,
|
|
|
|
aggregatorClient,
|
|
|
|
installationNamespaceK8sInformers.Core().V1().Secrets(),
|
|
|
|
controllerlib.WithInformer,
|
|
|
|
),
|
|
|
|
singletonWorker,
|
|
|
|
).
|
2020-08-09 17:04:05 +00:00
|
|
|
WithController(
|
|
|
|
apicerts.NewCertsObserverController(
|
|
|
|
serverInstallationNamespace,
|
Rename many of resources that are created in Kubernetes by Pinniped
New resource naming conventions:
- Do not repeat the Kind in the name,
e.g. do not call it foo-cluster-role-binding, just call it foo
- Names will generally start with a prefix to identify our component,
so when a user lists all objects of that kind, they can tell to which
component it is related,
e.g. `kubectl get configmaps` would list one named "pinniped-config"
- It should be possible for an operator to make the word "pinniped"
mostly disappear if they choose, by specifying the app_name in
values.yaml, to the extent that is practical (but not from APIService
names because those are hardcoded in golang)
- Each role/clusterrole and its corresponding binding have the same name
- Pinniped resource names that must be known by the server golang code
are passed to the code at run time via ConfigMap, rather than
hardcoded in the golang code. This also allows them to be prepended
with the app_name from values.yaml while creating the ConfigMap.
- Since the CLI `get-kubeconfig` command cannot guess the name of the
CredentialIssuerConfig resource in advance anymore, it lists all
CredentialIssuerConfig in the app's namespace and returns an error
if there is not exactly one found, and then uses that one regardless
of its name
2020-09-18 22:56:50 +00:00
|
|
|
namesConfig.ServingCertificateSecret,
|
2020-08-09 17:04:05 +00:00
|
|
|
dynamicCertProvider,
|
|
|
|
installationNamespaceK8sInformers.Core().V1().Secrets(),
|
2020-08-28 15:59:09 +00:00
|
|
|
controllerlib.WithInformer,
|
2020-08-07 21:49:04 +00:00
|
|
|
),
|
|
|
|
singletonWorker,
|
2020-08-19 20:15:45 +00:00
|
|
|
).
|
|
|
|
WithController(
|
|
|
|
apicerts.NewCertsExpirerController(
|
|
|
|
serverInstallationNamespace,
|
Rename many of resources that are created in Kubernetes by Pinniped
New resource naming conventions:
- Do not repeat the Kind in the name,
e.g. do not call it foo-cluster-role-binding, just call it foo
- Names will generally start with a prefix to identify our component,
so when a user lists all objects of that kind, they can tell to which
component it is related,
e.g. `kubectl get configmaps` would list one named "pinniped-config"
- It should be possible for an operator to make the word "pinniped"
mostly disappear if they choose, by specifying the app_name in
values.yaml, to the extent that is practical (but not from APIService
names because those are hardcoded in golang)
- Each role/clusterrole and its corresponding binding have the same name
- Pinniped resource names that must be known by the server golang code
are passed to the code at run time via ConfigMap, rather than
hardcoded in the golang code. This also allows them to be prepended
with the app_name from values.yaml while creating the ConfigMap.
- Since the CLI `get-kubeconfig` command cannot guess the name of the
CredentialIssuerConfig resource in advance anymore, it lists all
CredentialIssuerConfig in the app's namespace and returns an error
if there is not exactly one found, and then uses that one regardless
of its name
2020-09-18 22:56:50 +00:00
|
|
|
namesConfig.ServingCertificateSecret,
|
2020-08-19 20:15:45 +00:00
|
|
|
k8sClient,
|
|
|
|
installationNamespaceK8sInformers.Core().V1().Secrets(),
|
2020-08-28 15:59:09 +00:00
|
|
|
controllerlib.WithInformer,
|
2020-08-20 19:17:18 +00:00
|
|
|
servingCertRenewBefore,
|
2020-08-19 20:15:45 +00:00
|
|
|
),
|
|
|
|
singletonWorker,
|
2020-09-14 15:47:16 +00:00
|
|
|
).
|
|
|
|
WithController(
|
|
|
|
webhookcachefiller.New(
|
|
|
|
idpCache,
|
|
|
|
installationNamespacePinnipedInformers.IDP().V1alpha1().WebhookIdentityProviders(),
|
|
|
|
klogr.New(),
|
|
|
|
),
|
|
|
|
singletonWorker,
|
|
|
|
).
|
|
|
|
WithController(
|
|
|
|
webhookcachecleaner.New(
|
|
|
|
idpCache,
|
|
|
|
installationNamespacePinnipedInformers.IDP().V1alpha1().WebhookIdentityProviders(),
|
|
|
|
klogr.New(),
|
|
|
|
),
|
|
|
|
singletonWorker,
|
2020-08-07 21:49:04 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
// Return a function which starts the informers and controllers.
|
|
|
|
return func(ctx context.Context) {
|
2020-08-09 17:04:05 +00:00
|
|
|
kubePublicNamespaceK8sInformers.Start(ctx.Done())
|
|
|
|
installationNamespaceK8sInformers.Start(ctx.Done())
|
2020-08-20 17:54:15 +00:00
|
|
|
installationNamespacePinnipedInformers.Start(ctx.Done())
|
2020-08-09 17:04:05 +00:00
|
|
|
|
2020-09-15 18:52:08 +00:00
|
|
|
kubePublicNamespaceK8sInformers.WaitForCacheSync(ctx.Done())
|
|
|
|
installationNamespaceK8sInformers.WaitForCacheSync(ctx.Done())
|
|
|
|
installationNamespacePinnipedInformers.WaitForCacheSync(ctx.Done())
|
|
|
|
|
2020-08-07 21:49:04 +00:00
|
|
|
go controllerManager.Start(ctx)
|
|
|
|
}, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Create the k8s clients that will be used by the controllers.
|
2020-08-09 17:04:05 +00:00
|
|
|
func createClients() (
|
|
|
|
k8sClient *kubernetes.Clientset,
|
|
|
|
aggregatorClient *aggregatorclient.Clientset,
|
2020-08-20 17:54:15 +00:00
|
|
|
pinnipedClient *pinnipedclientset.Clientset,
|
2020-08-09 17:04:05 +00:00
|
|
|
err error,
|
|
|
|
) {
|
2020-08-19 18:21:07 +00:00
|
|
|
// Load the Kubernetes client configuration.
|
2020-08-07 21:49:04 +00:00
|
|
|
kubeConfig, err := restclient.InClusterConfig()
|
|
|
|
if err != nil {
|
|
|
|
return nil, nil, nil, fmt.Errorf("could not load in-cluster configuration: %w", err)
|
|
|
|
}
|
|
|
|
|
|
|
|
// explicitly use protobuf when talking to built-in kube APIs
|
|
|
|
protoKubeConfig := createProtoKubeConfig(kubeConfig)
|
|
|
|
|
|
|
|
// Connect to the core Kubernetes API.
|
2020-08-09 17:04:05 +00:00
|
|
|
k8sClient, err = kubernetes.NewForConfig(protoKubeConfig)
|
2020-08-07 21:49:04 +00:00
|
|
|
if err != nil {
|
|
|
|
return nil, nil, nil, fmt.Errorf("could not initialize Kubernetes client: %w", err)
|
|
|
|
}
|
|
|
|
|
|
|
|
// Connect to the Kubernetes aggregation API.
|
2020-08-09 17:04:05 +00:00
|
|
|
aggregatorClient, err = aggregatorclient.NewForConfig(protoKubeConfig)
|
2020-08-07 21:49:04 +00:00
|
|
|
if err != nil {
|
|
|
|
return nil, nil, nil, fmt.Errorf("could not initialize Kubernetes client: %w", err)
|
|
|
|
}
|
|
|
|
|
2020-08-20 17:54:15 +00:00
|
|
|
// Connect to the pinniped API.
|
2020-08-07 21:49:04 +00:00
|
|
|
// I think we can't use protobuf encoding here because we are using CRDs
|
|
|
|
// (for which protobuf encoding is not supported).
|
2020-08-20 17:54:15 +00:00
|
|
|
pinnipedClient, err = pinnipedclientset.NewForConfig(kubeConfig)
|
2020-08-07 21:49:04 +00:00
|
|
|
if err != nil {
|
2020-08-20 17:54:15 +00:00
|
|
|
return nil, nil, nil, fmt.Errorf("could not initialize pinniped client: %w", err)
|
2020-08-07 21:49:04 +00:00
|
|
|
}
|
|
|
|
|
Rename many of resources that are created in Kubernetes by Pinniped
New resource naming conventions:
- Do not repeat the Kind in the name,
e.g. do not call it foo-cluster-role-binding, just call it foo
- Names will generally start with a prefix to identify our component,
so when a user lists all objects of that kind, they can tell to which
component it is related,
e.g. `kubectl get configmaps` would list one named "pinniped-config"
- It should be possible for an operator to make the word "pinniped"
mostly disappear if they choose, by specifying the app_name in
values.yaml, to the extent that is practical (but not from APIService
names because those are hardcoded in golang)
- Each role/clusterrole and its corresponding binding have the same name
- Pinniped resource names that must be known by the server golang code
are passed to the code at run time via ConfigMap, rather than
hardcoded in the golang code. This also allows them to be prepended
with the app_name from values.yaml while creating the ConfigMap.
- Since the CLI `get-kubeconfig` command cannot guess the name of the
CredentialIssuerConfig resource in advance anymore, it lists all
CredentialIssuerConfig in the app's namespace and returns an error
if there is not exactly one found, and then uses that one regardless
of its name
2020-09-18 22:56:50 +00:00
|
|
|
//nolint: nakedret // Short function. Makes the order of return values more clear.
|
2020-08-09 17:04:05 +00:00
|
|
|
return
|
2020-08-07 21:49:04 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// Create the informers that will be used by the controllers.
|
|
|
|
func createInformers(
|
|
|
|
serverInstallationNamespace string,
|
|
|
|
k8sClient *kubernetes.Clientset,
|
2020-08-20 17:54:15 +00:00
|
|
|
pinnipedClient *pinnipedclientset.Clientset,
|
2020-08-09 17:04:05 +00:00
|
|
|
) (
|
|
|
|
kubePublicNamespaceK8sInformers k8sinformers.SharedInformerFactory,
|
|
|
|
installationNamespaceK8sInformers k8sinformers.SharedInformerFactory,
|
2020-08-20 17:54:15 +00:00
|
|
|
installationNamespacePinnipedInformers pinnipedinformers.SharedInformerFactory,
|
2020-08-09 17:04:05 +00:00
|
|
|
) {
|
|
|
|
kubePublicNamespaceK8sInformers = k8sinformers.NewSharedInformerFactoryWithOptions(
|
|
|
|
k8sClient,
|
|
|
|
defaultResyncInterval,
|
2020-08-21 16:55:44 +00:00
|
|
|
k8sinformers.WithNamespace(issuerconfig.ClusterInfoNamespace),
|
2020-08-09 17:04:05 +00:00
|
|
|
)
|
|
|
|
installationNamespaceK8sInformers = k8sinformers.NewSharedInformerFactoryWithOptions(
|
2020-08-07 21:49:04 +00:00
|
|
|
k8sClient,
|
|
|
|
defaultResyncInterval,
|
2020-08-09 17:04:05 +00:00
|
|
|
k8sinformers.WithNamespace(serverInstallationNamespace),
|
2020-08-07 21:49:04 +00:00
|
|
|
)
|
2020-08-20 17:54:15 +00:00
|
|
|
installationNamespacePinnipedInformers = pinnipedinformers.NewSharedInformerFactoryWithOptions(
|
|
|
|
pinnipedClient,
|
2020-08-07 21:49:04 +00:00
|
|
|
defaultResyncInterval,
|
2020-08-20 17:54:15 +00:00
|
|
|
pinnipedinformers.WithNamespace(serverInstallationNamespace),
|
2020-08-07 21:49:04 +00:00
|
|
|
)
|
2020-08-09 17:04:05 +00:00
|
|
|
return
|
2020-08-07 21:49:04 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// Returns a copy of the input config with the ContentConfig set to use protobuf.
|
|
|
|
// Do not use this config to communicate with any CRD based APIs.
|
|
|
|
func createProtoKubeConfig(kubeConfig *restclient.Config) *restclient.Config {
|
|
|
|
protoKubeConfig := restclient.CopyConfig(kubeConfig)
|
|
|
|
const protoThenJSON = runtime.ContentTypeProtobuf + "," + runtime.ContentTypeJSON
|
|
|
|
protoKubeConfig.AcceptContentTypes = protoThenJSON
|
|
|
|
protoKubeConfig.ContentType = runtime.ContentTypeProtobuf
|
|
|
|
return protoKubeConfig
|
|
|
|
}
|