- Sort Score
- Result 10 results
- Languages All
Results 171 - 180 of 704 for 1release (0.08 sec)
-
helm-releases/minio-5.0.13.tgz
.Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Jul 09 07:13:05 UTC 2023 - 20.3K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.27.md
https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize%2Fv5.0.0 and https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize%2Fv5.0.1. This is a new major release of kustomize, so there are a few backwards-incompatible changes, most of which are rare use cases, bug fixes with side effects, or things that have been deprecated for multiple releases already:
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Jul 17 07:48:22 UTC 2024 - 466.3K bytes - Viewed (1) -
helm-releases/minio-5.3.0.tgz
}} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.{{ .Values.clusterDomain }} To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kub...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Oct 11 12:21:05 UTC 2024 - 21.7K bytes - Viewed (0) -
docker-buildx.sh
--build-arg RELEASE="${release}" \ -t "minio/minio:${release}-cpuv1" \ -t "quay.io/minio/minio:${release}-cpuv1" \ --platform=linux/arm64,linux/amd64,linux/ppc64le \ -f Dockerfile.release.old_cpu . docker buildx prune -f docker buildx build --push --no-cache \ --build-arg RELEASE="${release}" \ -t "minio/minio:${release}.fips" \ -t "quay.io/minio/minio:${release}.fips" \ --platform=linux/amd64 -f Dockerfile.release.fips .
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Oct 13 14:06:17 UTC 2024 - 1.2K bytes - Viewed (0) -
doc/godebug.md
--- title: "Go, Backwards Compatibility, and GODEBUG" layout: article --- <!-- This document is kept in the Go repo, not x/website, because it documents the full list of known GODEBUG settings, which are tied to a specific release. --> ## Introduction {#intro} Go's emphasis on backwards compatibility is one of its key strengths. There are, however, times when we cannot maintain complete compatibility.
Registered: Tue Nov 05 11:13:11 UTC 2024 - Last Modified: Mon Oct 28 14:46:33 UTC 2024 - 17.2K bytes - Viewed (0) -
CHANGELOG/OWNERS
no_parent_owners: true approvers: - release-engineering-approvers - release-managers - AuraSinis # 1.24 Release Notes Lead - cici37 # 1.23 Release Notes Lead - csantanapr # 1.25 Release Notes Lead - harshanarayana # 1.27 Release Notes Lead - ramrodo # 1.26 Release Notes Lead - sanchita-07 # 1.28 Release Notes Lead - fsmunoz # 1.29 Release Notes Lead - rashansmith # 1.30 Release Notes Lead reviewers: - release-managers
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Jan 24 16:11:28 UTC 2024 - 801 bytes - Viewed (0) -
doc/README.md
Then open http://localhost:6060/doc/next. Refresh the page to see your latest edits. ## For the release team The `relnote` tool, at `golang.org/x/build/cmd/relnote`, operates on the files in `doc/next`. As a release cycle nears completion, run `relnote todo` to get a list of unfinished release note work. To prepare the release notes for a release, run `relnote generate`. That will merge the `.md` files in `next` into a single file.
Registered: Tue Nov 05 11:13:11 UTC 2024 - Last Modified: Mon Jul 22 17:55:04 UTC 2024 - 3.1K bytes - Viewed (0) -
.teamcity/src/main/kotlin/promotion/PublishRelease.kt
requiredConfirmationCode = "rc", init = { id("Promotion_ReleaseCandidate") name = "Release - Release Candidate" description = "Promotes the latest successful change on 'release' as a new release candidate" } ) class PublishMilestone(branch: VersionedSettingsBranch) : PublishRelease( promotedBranch = branch.branchName, prepTask = "prepMilestone",
Registered: Wed Nov 06 11:36:14 UTC 2024 - Last Modified: Tue Dec 05 00:08:14 UTC 2023 - 3.5K bytes - Viewed (0) -
RELEASE_BRANCHES.md
# Release Branches Release branches have a name of `release-MAJOR.MINOR`. Essential Istio repositories are branched from master roughly 4 weeks prior to a new release. The `istio/istio.io` repository does not get branched until the release is ready for publication. This document outlines getting in new features after a new branch has been cut and the process for getting a PR merged in before and after the first public release. # Feature Freeze
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Sep 16 21:14:17 UTC 2024 - 4.2K bytes - Viewed (0) -
docs/site-replication/run-ssec-object-replication.sh
echo "done" if [ ! -f ./mc ]; then echo -n "Downloading MinIO client ..." wget -O mc https://dl.min.io/client/mc/release/linux-amd64/mc && chmod +x mc echo "done" fi export MC_HOST_minio1=https://minio:minio123@localhost:9001 export MC_HOST_minio2=https://minio:minio123@localhost:9002 ./mc ready minio1 --insecure
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Sep 24 08:03:58 UTC 2024 - 9.9K bytes - Viewed (0)