- Sort Score
- Result 10 results
- Languages All
Results 71 - 80 of 430 for Secrets (0.1 sec)
-
istioctl/pkg/writer/envoy/configdump/testdata/endpoint/emptyfilter_output.txt
10.244.0.195:9080 HEALTHY outbound|9080||reviews.default.svc.cluster.local ./var/run/secrets/workload-spiffe-uds/socket HEALTHY sds-grpc 10.244.0.188:11800 HEALTHY outbound|11800||skywalking-oap.skywalking.svc.cluster.local
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Apr 21 14:17:23 UTC 2023 - 4.5K bytes - Viewed (0) -
.github/workflows/release-branch-cherrypick.yml
committer: TensorFlow Release Automation <******@****.***> token: ${{ secrets.JENKINS_TOKEN }} base: ${{ github.event.inputs.release_branch }} branch: ${{ github.event.inputs.release_branch }}-${{ steps.cherrypick.outputs.SHORTSHA }} reviewers: learning-to-play body: |
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Fri Nov 01 08:40:10 UTC 2024 - 3.1K bytes - Viewed (0) -
architecture/networking/pilot.md
This is rooted in the Multicluster Secret controller, which reads `kubeconfig` files (stored as `Secrets`), and creating Kubernetes clients for each. The controller allows registering handlers which can process Add/Update/Delete of clusters. This has two implementations: * The Credentials controller is responsible for reading TLS certificates, stored as Secrets.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Feb 07 17:53:24 UTC 2024 - 19.1K bytes - Viewed (0) -
helm-releases/minio-3.6.0.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Mar 13 22:44:21 UTC 2022 - 17.9K bytes - Viewed (0) -
.github/workflows/stale.yml
runs-on: ubuntu-latest env: ACTIONS_STEP_DEBUG: true steps: - name: Close Stale Issues uses: actions/stale@v8 with: repo-token: ${{ secrets.GITHUB_TOKEN }} stale-issue-message: "This issue has been automatically marked as stale because it has been open 360 days with no activity. Remove stale label or comment or this will be closed in 180 days"
Registered: Sun Nov 03 09:35:10 UTC 2024 - Last Modified: Tue Apr 11 02:27:05 UTC 2023 - 972 bytes - Viewed (0) -
internal/kms/config.go
if err != nil && !os.IsNotExist(err) { return nil, err } if os.IsNotExist(err) { // Relative path where "/run/secrets" is the default docker path for secrets b, err = os.ReadFile(filepath.Join("/run/secrets", env.Get(EnvKMSSecretKeyFile, ""))) } if err != nil { return nil, err } s = string(b) } else { s = env.Get(EnvKMSSecretKey, "") }
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Aug 15 11:46:39 UTC 2024 - 14.2K bytes - Viewed (0) -
samples/guide/src/main/java/okhttp3/recipes/kt/Authenticate.kt
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Mon Jan 08 01:13:22 UTC 2024 - 1.9K bytes - Viewed (0) -
helm-releases/minio-3.6.2.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Mar 17 18:30:55 UTC 2022 - 17.9K bytes - Viewed (0) -
.github/workflows/build.yml
run: ./gradlew clean publish --stacktrace env: ORG_GRADLE_PROJECT_mavenCentralUsername: ${{ secrets.SONATYPE_NEXUS_USERNAME }} ORG_GRADLE_PROJECT_mavenCentralPassword: ${{ secrets.SONATYPE_NEXUS_PASSWORD }} ORG_GRADLE_PROJECT_signingInMemoryKey: ${{ secrets.ARTIFACT_SIGNING_PRIVATE_KEY }} validation: name: "Validation" runs-on: ubuntu-latest steps:
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Sat Aug 17 10:05:29 UTC 2024 - 17.2K bytes - Viewed (0) -
helm-releases/minio-2.0.1.tgz
displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Aug 31 09:09:09 UTC 2021 - 13.6K bytes - Viewed (0)