2020-09-16 14:19:51 +00:00
|
|
|
// Copyright 2020 the Pinniped contributors. All Rights Reserved.
|
|
|
|
|
// SPDX-License-Identifier: Apache-2.0
|
2020-07-14 15:50:14 +00:00
|
|
|
|
2020-10-15 19:40:56 +00:00
|
|
|
package concierge
|
2020-07-14 15:50:14 +00:00
|
|
|
|
|
|
|
|
import (
|
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
|
|
|
"io/ioutil"
|
|
|
|
|
"os"
|
2020-07-14 15:50:14 +00:00
|
|
|
"testing"
|
|
|
|
|
|
|
|
|
|
"github.com/stretchr/testify/require"
|
|
|
|
|
|
2020-09-18 23:39:58 +00:00
|
|
|
"go.pinniped.dev/internal/here"
|
2020-07-14 15:50:14 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
func TestFromPath(t *testing.T) {
|
2020-08-03 14:17:11 +00:00
|
|
|
tests := []struct {
|
|
|
|
|
name 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
|
|
|
yaml string
|
2020-10-15 19:40:56 +00:00
|
|
|
wantConfig *Config
|
2020-08-20 19:17:18 +00:00
|
|
|
wantError string
|
2020-08-03 14:17:11 +00:00
|
|
|
}{
|
|
|
|
|
{
|
|
|
|
|
name: "Happy",
|
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
|
|
|
yaml: here.Doc(`
|
|
|
|
|
---
|
|
|
|
|
discovery:
|
|
|
|
|
url: https://some.discovery/url
|
|
|
|
|
api:
|
|
|
|
|
servingCertificate:
|
|
|
|
|
durationSeconds: 3600
|
|
|
|
|
renewBeforeSeconds: 2400
|
|
|
|
|
names:
|
2020-10-09 21:25:34 +00:00
|
|
|
servingCertificateSecret: pinniped-concierge-api-tls-serving-certificate
|
2020-11-02 21:39:43 +00:00
|
|
|
credentialIssuer: pinniped-config
|
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
|
|
|
apiService: pinniped-api
|
2020-09-21 18:16:14 +00:00
|
|
|
kubeCertAgentPrefix: kube-cert-agent-prefix
|
2020-10-15 17:14:23 +00:00
|
|
|
labels:
|
|
|
|
|
myLabelKey1: myLabelValue1
|
|
|
|
|
myLabelKey2: myLabelValue2
|
2020-09-21 18:16:14 +00:00
|
|
|
KubeCertAgent:
|
|
|
|
|
namePrefix: kube-cert-agent-name-prefix-
|
|
|
|
|
image: kube-cert-agent-image
|
2020-09-24 19:52:05 +00:00
|
|
|
imagePullSecrets: [kube-cert-agent-image-pull-secret]
|
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
|
|
|
`),
|
2020-10-15 19:40:56 +00:00
|
|
|
wantConfig: &Config{
|
|
|
|
|
DiscoveryInfo: DiscoveryInfoSpec{
|
2020-08-03 14:17:11 +00:00
|
|
|
URL: stringPtr("https://some.discovery/url"),
|
|
|
|
|
},
|
2020-10-15 19:40:56 +00:00
|
|
|
APIConfig: APIConfigSpec{
|
|
|
|
|
ServingCertificateConfig: ServingCertificateConfigSpec{
|
2020-08-20 19:17:18 +00:00
|
|
|
DurationSeconds: int64Ptr(3600),
|
|
|
|
|
RenewBeforeSeconds: int64Ptr(2400),
|
|
|
|
|
},
|
|
|
|
|
},
|
2020-10-15 19:40:56 +00:00
|
|
|
NamesConfig: NamesConfigSpec{
|
2020-10-09 21:25:34 +00:00
|
|
|
ServingCertificateSecret: "pinniped-concierge-api-tls-serving-certificate",
|
2020-11-02 21:39:43 +00:00
|
|
|
CredentialIssuer: "pinniped-config",
|
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
|
|
|
APIService: "pinniped-api",
|
|
|
|
|
},
|
2020-10-15 17:14:23 +00:00
|
|
|
Labels: map[string]string{
|
|
|
|
|
"myLabelKey1": "myLabelValue1",
|
|
|
|
|
"myLabelKey2": "myLabelValue2",
|
|
|
|
|
},
|
2020-10-15 19:40:56 +00:00
|
|
|
KubeCertAgentConfig: KubeCertAgentSpec{
|
2020-09-24 19:52:05 +00:00
|
|
|
NamePrefix: stringPtr("kube-cert-agent-name-prefix-"),
|
|
|
|
|
Image: stringPtr("kube-cert-agent-image"),
|
|
|
|
|
ImagePullSecrets: []string{"kube-cert-agent-image-pull-secret"},
|
2020-09-21 18:16:14 +00:00
|
|
|
},
|
2020-08-03 14:17:11 +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
|
|
|
name: "When only the required fields are present, causes other fields to be defaulted",
|
|
|
|
|
yaml: here.Doc(`
|
|
|
|
|
---
|
|
|
|
|
names:
|
2020-10-09 21:25:34 +00:00
|
|
|
servingCertificateSecret: pinniped-concierge-api-tls-serving-certificate
|
2020-11-02 21:39:43 +00:00
|
|
|
credentialIssuer: pinniped-config
|
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
|
|
|
apiService: pinniped-api
|
|
|
|
|
`),
|
2020-10-15 19:40:56 +00:00
|
|
|
wantConfig: &Config{
|
|
|
|
|
DiscoveryInfo: DiscoveryInfoSpec{
|
2020-08-03 14:17:11 +00:00
|
|
|
URL: nil,
|
|
|
|
|
},
|
2020-10-15 19:40:56 +00:00
|
|
|
APIConfig: APIConfigSpec{
|
|
|
|
|
ServingCertificateConfig: ServingCertificateConfigSpec{
|
2020-08-20 19:17:18 +00:00
|
|
|
DurationSeconds: int64Ptr(60 * 60 * 24 * 365), // about a year
|
|
|
|
|
RenewBeforeSeconds: int64Ptr(60 * 60 * 24 * 30 * 9), // about 9 months
|
|
|
|
|
},
|
|
|
|
|
},
|
2020-10-15 19:40:56 +00:00
|
|
|
NamesConfig: NamesConfigSpec{
|
2020-10-09 21:25:34 +00:00
|
|
|
ServingCertificateSecret: "pinniped-concierge-api-tls-serving-certificate",
|
2020-11-02 21:39:43 +00:00
|
|
|
CredentialIssuer: "pinniped-config",
|
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
|
|
|
APIService: "pinniped-api",
|
|
|
|
|
},
|
2020-10-15 17:14:23 +00:00
|
|
|
Labels: map[string]string{},
|
2020-10-15 19:40:56 +00:00
|
|
|
KubeCertAgentConfig: KubeCertAgentSpec{
|
2020-09-21 18:16:14 +00:00
|
|
|
NamePrefix: stringPtr("pinniped-kube-cert-agent-"),
|
|
|
|
|
Image: stringPtr("debian:latest"),
|
|
|
|
|
},
|
2020-08-03 14:17:11 +00:00
|
|
|
},
|
2020-07-14 15:50:14 +00:00
|
|
|
},
|
2020-08-20 19:17:18 +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
|
|
|
name: "Empty",
|
|
|
|
|
yaml: here.Doc(``),
|
2020-11-02 21:39:43 +00:00
|
|
|
wantError: "validate names: missing required names: servingCertificateSecret, credentialIssuer, apiService",
|
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
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
name: "Missing apiService name",
|
|
|
|
|
yaml: here.Doc(`
|
|
|
|
|
---
|
|
|
|
|
names:
|
2020-10-09 21:25:34 +00:00
|
|
|
servingCertificateSecret: pinniped-concierge-api-tls-serving-certificate
|
2020-11-02 21:39:43 +00:00
|
|
|
credentialIssuer: pinniped-config
|
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
|
|
|
`),
|
|
|
|
|
wantError: "validate names: missing required names: apiService",
|
|
|
|
|
},
|
|
|
|
|
{
|
2020-11-02 21:39:43 +00:00
|
|
|
name: "Missing credentialIssuer name",
|
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
|
|
|
yaml: here.Doc(`
|
|
|
|
|
---
|
|
|
|
|
names:
|
2020-10-09 21:25:34 +00:00
|
|
|
servingCertificateSecret: pinniped-concierge-api-tls-serving-certificate
|
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
|
|
|
apiService: pinniped-api
|
|
|
|
|
`),
|
2020-11-02 21:39:43 +00:00
|
|
|
wantError: "validate names: missing required names: credentialIssuer",
|
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
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
name: "Missing servingCertificateSecret name",
|
|
|
|
|
yaml: here.Doc(`
|
|
|
|
|
---
|
|
|
|
|
names:
|
2020-11-02 21:39:43 +00:00
|
|
|
credentialIssuer: pinniped-config
|
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
|
|
|
apiService: pinniped-api
|
|
|
|
|
`),
|
|
|
|
|
wantError: "validate names: missing required names: servingCertificateSecret",
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
name: "InvalidDurationRenewBefore",
|
|
|
|
|
yaml: here.Doc(`
|
|
|
|
|
---
|
|
|
|
|
api:
|
|
|
|
|
servingCertificate:
|
|
|
|
|
durationSeconds: 2400
|
|
|
|
|
renewBeforeSeconds: 3600
|
|
|
|
|
names:
|
2020-10-09 21:25:34 +00:00
|
|
|
servingCertificateSecret: pinniped-concierge-api-tls-serving-certificate
|
2020-11-02 21:39:43 +00:00
|
|
|
credentialIssuer: pinniped-config
|
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
|
|
|
apiService: pinniped-api
|
|
|
|
|
`),
|
2020-08-20 19:17:18 +00:00
|
|
|
wantError: "validate api: durationSeconds cannot be smaller than renewBeforeSeconds",
|
|
|
|
|
},
|
2020-08-20 22:14:07 +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
|
|
|
name: "NegativeRenewBefore",
|
|
|
|
|
yaml: here.Doc(`
|
|
|
|
|
---
|
|
|
|
|
api:
|
|
|
|
|
servingCertificate:
|
|
|
|
|
durationSeconds: 2400
|
|
|
|
|
renewBeforeSeconds: -10
|
|
|
|
|
names:
|
2020-10-09 21:25:34 +00:00
|
|
|
servingCertificateSecret: pinniped-concierge-api-tls-serving-certificate
|
2020-11-02 21:39:43 +00:00
|
|
|
credentialIssuer: pinniped-config
|
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
|
|
|
apiService: pinniped-api
|
|
|
|
|
`),
|
2020-08-20 22:14:07 +00:00
|
|
|
wantError: "validate api: renewBefore must be positive",
|
|
|
|
|
},
|
|
|
|
|
{
|
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
|
|
|
name: "ZeroRenewBefore",
|
|
|
|
|
yaml: here.Doc(`
|
|
|
|
|
---
|
|
|
|
|
api:
|
|
|
|
|
servingCertificate:
|
|
|
|
|
durationSeconds: 2400
|
|
|
|
|
renewBeforeSeconds: -10
|
|
|
|
|
names:
|
2020-10-09 21:25:34 +00:00
|
|
|
servingCertificateSecret: pinniped-concierge-api-tls-serving-certificate
|
2020-11-02 21:39:43 +00:00
|
|
|
credentialIssuer: pinniped-config
|
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
|
|
|
apiService: pinniped-api
|
|
|
|
|
`),
|
2020-08-20 22:14:07 +00:00
|
|
|
wantError: "validate api: renewBefore must be positive",
|
|
|
|
|
},
|
2020-08-03 14:17:11 +00:00
|
|
|
}
|
|
|
|
|
for _, test := range tests {
|
|
|
|
|
test := test
|
|
|
|
|
t.Run(test.name, func(t *testing.T) {
|
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
|
|
|
// Write yaml to temp file
|
|
|
|
|
f, err := ioutil.TempFile("", "pinniped-test-config-yaml-*")
|
|
|
|
|
require.NoError(t, err)
|
|
|
|
|
defer func() {
|
|
|
|
|
err := os.Remove(f.Name())
|
|
|
|
|
require.NoError(t, err)
|
|
|
|
|
}()
|
|
|
|
|
_, err = f.WriteString(test.yaml)
|
|
|
|
|
require.NoError(t, err)
|
|
|
|
|
err = f.Close()
|
|
|
|
|
require.NoError(t, err)
|
|
|
|
|
|
|
|
|
|
// Test FromPath()
|
|
|
|
|
config, err := FromPath(f.Name())
|
|
|
|
|
|
2020-08-20 19:17:18 +00:00
|
|
|
if test.wantError != "" {
|
|
|
|
|
require.EqualError(t, err, test.wantError)
|
|
|
|
|
} else {
|
|
|
|
|
require.NoError(t, err)
|
|
|
|
|
require.Equal(t, test.wantConfig, config)
|
|
|
|
|
}
|
2020-08-03 14:17:11 +00:00
|
|
|
})
|
|
|
|
|
}
|
|
|
|
|
}
|