ContainerImage.Pinniped/test/cluster_capabilities/tkgs.yaml

# Copyright 2020-2021 the Pinniped contributors. All Rights Reserved.
# SPDX-License-Identifier: Apache-2.0

# The name of the cluster type.
kubernetesDistribution: TKGS

# Describe the capabilities of the cluster against which the integration tests will run.
capabilities:

  # Is it possible to borrow the cluster's signing key from the kube API server?
  clusterSigningKeyIsAvailable: true

  # Will the cluster successfully provision a load balancer if requested?
  hasExternalLoadBalancerProvider: true

  # Does the cluster allow requests without authentication?
  # https://kubernetes.io/docs/reference/access-authn-authz/authentication/#anonymous-requests
  anonymousAuthenticationSupported: true

  # Are LDAP ports on the Internet reachable without interference from network firewalls or proxies?
  canReachInternetLDAPPorts: true
Introduce clusterhost package to determine whether a cluster has control plane nodes Also added hasExternalLoadBalancerProvider key to cluster capabilities for integration testing. Signed-off-by: Ryan Richard <richardry@vmware.com> 2021-02-05 17:01:39 -08:00			`# Copyright 2020-2021 the Pinniped contributors. All Rights Reserved.`
Upon pod startup, update the Status of CredentialIssuerConfig - Indicate the success or failure of the cluster signing key strategy - Also introduce the concept of "capabilities" of an integration test cluster to allow the integration tests to be run against clusters that do or don't allow the borrowing of the cluster signing key - Tests that are not expected to pass on clusters that lack the borrowing of the signing key capability are now ignored by calling the new library.SkipUnlessClusterHasCapability test helper - Rename library.Getenv to library.GetEnv - Add copyrights where they were missing 2020-08-24 18:07:34 -07:00			`# SPDX-License-Identifier: Apache-2.0`

Run the LDAP client's integration tests only on Kind TestSimultaneousLDAPRequestsOnSingleProvider proved to be unreliable on AKS due to some kind of kubectl port-forward issue, so only run the LDAP client's integration tests on Kind. They are testing the integration between the client code and the OpenLDAP test server, not testing anything about Kubernetes, so running only on Kind should give us sufficient test coverage. 2021-07-08 11:10:53 -07:00			`# The name of the cluster type.`
			`kubernetesDistribution: TKGS`

Upon pod startup, update the Status of CredentialIssuerConfig - Indicate the success or failure of the cluster signing key strategy - Also introduce the concept of "capabilities" of an integration test cluster to allow the integration tests to be run against clusters that do or don't allow the borrowing of the cluster signing key - Tests that are not expected to pass on clusters that lack the borrowing of the signing key capability are now ignored by calling the new library.SkipUnlessClusterHasCapability test helper - Rename library.Getenv to library.GetEnv - Add copyrights where they were missing 2020-08-24 18:07:34 -07:00			`# Describe the capabilities of the cluster against which the integration tests will run.`
			`capabilities:`

			`# Is it possible to borrow the cluster's signing key from the kube API server?`
			`clusterSigningKeyIsAvailable: true`
Introduce clusterhost package to determine whether a cluster has control plane nodes Also added hasExternalLoadBalancerProvider key to cluster capabilities for integration testing. Signed-off-by: Ryan Richard <richardry@vmware.com> 2021-02-05 17:01:39 -08:00
			`# Will the cluster successfully provision a load balancer if requested?`
			`hasExternalLoadBalancerProvider: true`
Merge branch 'main' of github.com:vmware-tanzu/pinniped into impersonation-proxy Signed-off-by: Matt Moyer <moyerm@vmware.com> 2021-03-16 14:35:07 -05:00
Describe "anonymousAuthenticationSupported" test cluster capability and add more managed cluster types. This new capability describes whether a cluster is expected to allow anonymous requests (most do since k8s 1.6.x, but AKS has it disabled). This commit also contains new capability YAML files for AKS and EKS, mostly to document publicly how we expect our tests to function in those environments. Signed-off-by: Matt Moyer <moyerm@vmware.com> 2021-03-16 13:54:29 -05:00			`# Does the cluster allow requests without authentication?`
			`# https://kubernetes.io/docs/reference/access-authn-authz/authentication/#anonymous-requests`
			`anonymousAuthenticationSupported: true`
Enable skipping of LDAP int tests when a firewall will block them 2021-05-28 16:12:57 -07:00
			`# Are LDAP ports on the Internet reachable without interference from network firewalls or proxies?`
Run the LDAP client's integration tests only on Kind TestSimultaneousLDAPRequestsOnSingleProvider proved to be unreliable on AKS due to some kind of kubectl port-forward issue, so only run the LDAP client's integration tests on Kind. They are testing the integration between the client code and the OpenLDAP test server, not testing anything about Kubernetes, so running only on Kind should give us sufficient test coverage. 2021-07-08 11:10:53 -07:00			`canReachInternetLDAPPorts: true`