ContainerImage.Pinniped/hack/lib/kind-config/single-node.yaml

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
  - role: control-plane
    extraPortMappings:
    - protocol: TCP
      # This same port number is hardcoded in the integration test setup
      # when creating a Service on a kind cluster. It is used to talk to
      # the supervisor app via HTTPS.
      containerPort: 31243
      hostPort: 12344
      listenAddress: 127.0.0.1
    - protocol: TCP
      # This same port number is hardcoded in the integration test setup
      # when creating a Service on a kind cluster. It is used to talk to
      # the supervisor app via HTTP.
      containerPort: 31234
      hostPort: 12345
      listenAddress: 127.0.0.1
    - protocol: TCP
      # This same port number is hardcoded in the integration test setup
      # when creating a Service on a kind cluster. It is used to talk to
      # the Dex app.
      containerPort: 31235
      hostPort: 12346
      listenAddress: 127.0.0.1
Add integration test for the OIDC discovery endpoint - Intended to be a red test in this commit; will make it go green in a future commit - Enhance env.go and prepare-for-integration-tests.sh to make it possible to write integration tests for the supervisor app by setting more env vars and by exposing the service to the kind host on a localhost port - Add `--clean` option to prepare-for-integration-tests.sh to make it easier to start fresh - Make prepare-for-integration-tests.sh advise you to run `go test -v -count 1 ./test/integration` because this does not buffer the test output - Make concierge_api_discovery_test.go pass by adding expectations for the new OIDCProviderConfig type 2020-10-07 00:53:29 +00:00			`kind: Cluster`
			`apiVersion: kind.x-k8s.io/v1alpha4`
			`nodes:`
			`- role: control-plane`
Add Dex to our integration test environment and use it to test the CLI. Signed-off-by: Matt Moyer <moyerm@vmware.com> 2020-10-13 21:09:13 +00:00			`extraPortMappings:`
			`- protocol: TCP`
Add comments for magic 31234 port Also delete hack/lib/kind-config/multi-node.yaml since we don't think we will use it... Signed-off-by: Andrew Keesler <akeesler@vmware.com> 2020-10-22 21:53:40 +00:00			`# This same port number is hardcoded in the integration test setup`
			`# when creating a Service on a kind cluster. It is used to talk to`
Supervisor listens for HTTPS on port 443 with configurable TLS certs - TLS certificates can be configured on the OIDCProviderConfig using the `secretName` field. - When listening for incoming TLS connections, choose the TLS cert based on the SNI hostname of the incoming request. - Because SNI hostname information on incoming requests does not include the port number of the request, we add a validation that OIDCProviderConfigs where the issuer hostnames (not including port number) are the same must use the same `secretName`. - Note that this approach does not yet support requests made to an IP address instead of a hostname. Also note that `localhost` is considered a hostname by SNI. - Add port 443 as a container port to the pod spec. - A new controller watches for TLS secrets and caches them in memory. That same in-memory cache is used while servicing incoming connections on the TLS port. - Make it easy to configure both port 443 and/or port 80 for various Service types using our ytt templates for the supervisor. - When deploying to kind, add another nodeport and forward it to the host on another port to expose our new HTTPS supervisor port to the host. 2020-10-27 00:03:26 +00:00			`# the supervisor app via HTTPS.`
			`containerPort: 31243`
			`hostPort: 12344`
			`listenAddress: 127.0.0.1`
			`- protocol: TCP`
			`# This same port number is hardcoded in the integration test setup`
			`# when creating a Service on a kind cluster. It is used to talk to`
			`# the supervisor app via HTTP.`
Add Dex to our integration test environment and use it to test the CLI. Signed-off-by: Matt Moyer <moyerm@vmware.com> 2020-10-13 21:09:13 +00:00			`containerPort: 31234`
			`hostPort: 12345`
			`listenAddress: 127.0.0.1`
			`- protocol: TCP`
Add comments for magic 31234 port Also delete hack/lib/kind-config/multi-node.yaml since we don't think we will use it... Signed-off-by: Andrew Keesler <akeesler@vmware.com> 2020-10-22 21:53:40 +00:00			`# This same port number is hardcoded in the integration test setup`
			`# when creating a Service on a kind cluster. It is used to talk to`
			`# the Dex app.`
Add Dex to our integration test environment and use it to test the CLI. Signed-off-by: Matt Moyer <moyerm@vmware.com> 2020-10-13 21:09:13 +00:00			`containerPort: 31235`
			`hostPort: 12346`
			`listenAddress: 127.0.0.1`