From f696cb452b963d2668cc756690741c69cb03ea24 Mon Sep 17 00:00:00 2001 From: Thomas Tendyck Date: Wed, 11 Oct 2023 13:13:28 +0200 Subject: [PATCH] s3proxy: remove unnecessary pull secret --- docs/docs/getting-started/examples/filestash-s3proxy.md | 3 +-- .../getting-started/examples/filestash-s3proxy.md | 3 +-- s3proxy/deploy/README.md | 4 ++-- s3proxy/deploy/deployment-s3proxy.yaml | 2 -- 4 files changed, 4 insertions(+), 8 deletions(-) diff --git a/docs/docs/getting-started/examples/filestash-s3proxy.md b/docs/docs/getting-started/examples/filestash-s3proxy.md index 6dd67f28c..440c4b58a 100644 --- a/docs/docs/getting-started/examples/filestash-s3proxy.md +++ b/docs/docs/getting-started/examples/filestash-s3proxy.md @@ -23,8 +23,6 @@ spec: labels: app: filestash spec: - imagePullSecrets: - - name: regcred hostAliases: - ip: $(kubectl get svc s3proxy-service -o=jsonpath='{.spec.clusterIP}') hostnames: @@ -54,6 +52,7 @@ If you followed the s3proxy [Deployment](../../workflows/s3proxy.md#deployment) To use other regions than `eu-west-1`, add more entries to `hostAliases` for all regions you require. Use the same IP for those entries. For example to add `us-east-1` add: + ```yaml - ip: $(kubectl get svc s3proxy-service -o=jsonpath='{.spec.clusterIP}') hostnames: diff --git a/docs/versioned_docs/version-2.12/getting-started/examples/filestash-s3proxy.md b/docs/versioned_docs/version-2.12/getting-started/examples/filestash-s3proxy.md index 6dd67f28c..440c4b58a 100644 --- a/docs/versioned_docs/version-2.12/getting-started/examples/filestash-s3proxy.md +++ b/docs/versioned_docs/version-2.12/getting-started/examples/filestash-s3proxy.md @@ -23,8 +23,6 @@ spec: labels: app: filestash spec: - imagePullSecrets: - - name: regcred hostAliases: - ip: $(kubectl get svc s3proxy-service -o=jsonpath='{.spec.clusterIP}') hostnames: @@ -54,6 +52,7 @@ If you followed the s3proxy [Deployment](../../workflows/s3proxy.md#deployment) To use other regions than `eu-west-1`, add more entries to `hostAliases` for all regions you require. Use the same IP for those entries. For example to add `us-east-1` add: + ```yaml - ip: $(kubectl get svc s3proxy-service -o=jsonpath='{.spec.clusterIP}') hostnames: diff --git a/s3proxy/deploy/README.md b/s3proxy/deploy/README.md index e95d80206..6a36541f7 100644 --- a/s3proxy/deploy/README.md +++ b/s3proxy/deploy/README.md @@ -4,6 +4,7 @@ The VPN is a feature of Constellation and will not be present by default in other environments. Disclaimer: the following steps will be automated next. + - Within `constellation/build`: `bazel run //:devbuild` - Copy the container name displayed for the s3proxy image. Look for the line starting with `[@//bazel/release:s3proxy_push]`. - Replace the image key in `deployment-s3proxy.yaml` with the image value you just copied. Use the sha256 hash instead of the tag to make sure you use the latest image. @@ -32,8 +33,6 @@ spec: labels: app: filestash spec: - imagePullSecrets: - - name: regcred hostAliases: - ip: $(kubectl get svc s3proxy-service -o=jsonpath='{.spec.clusterIP}') hostnames: @@ -60,4 +59,5 @@ $ kubectl apply -f deployment-filestash.yaml ``` Afterwards you can use a port forward to access the Filestash pod: + - `kubectl port-forward pod/$(kubectl get pod --selector='app=filestash' -o=jsonpath='{.items[*].metadata.name}') 8443:8443` diff --git a/s3proxy/deploy/deployment-s3proxy.yaml b/s3proxy/deploy/deployment-s3proxy.yaml index 49ca522ac..642168bf7 100644 --- a/s3proxy/deploy/deployment-s3proxy.yaml +++ b/s3proxy/deploy/deployment-s3proxy.yaml @@ -43,8 +43,6 @@ spec: labels: app: s3proxy spec: - imagePullSecrets: - - name: regcred containers: - name: s3proxy image: ghcr.io/edgelesssys/constellation/s3proxy:v2.12.0