- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for texts (0.12 sec)
-
manifests/addons/gen.sh
# See the License for the specific language governing permissions and # limitations under the License. WD=$(dirname "$0") WD=$(cd "$WD"; pwd) set -eux # This script sets up the plain text rendered deployments for addons # See samples/addons/README.md for more information ADDONS="${WD}/../../samples/addons" DASHBOARDS="${WD}/dashboards" mkdir -p "${ADDONS}" TMP=$(mktemp -d)
Shell Script - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 09 21:40:53 GMT 2024 - 3.2K bytes - Viewed (0) -
common/scripts/setup_env.sh
KUBECONFIG="${container_kubeconfig%?}" fi # LOCAL_OUT should point to architecture where we are currently running versus the desired. # This is used when we need to run a build artifact during tests or later as part of another # target. if [[ "${FOR_BUILD_CONTAINER:-0}" -eq "1" ]]; then # Override variables with container specific TARGET_OUT=${CONTAINER_TARGET_OUT} TARGET_OUT_LINUX=${CONTAINER_TARGET_OUT_LINUX}
Shell Script - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu May 02 16:31:40 GMT 2024 - 7.6K bytes - Viewed (0) -
common/scripts/kind_provisioner.sh
KUBECONFIG="${CLUSTER_KUBECONFIG}" setup_kind_cluster "${CLUSTER_NAME}" "${IMAGE}" "${CLUSTER_YAML}" "true" "false" # Kind currently supports getting a kubeconfig for internal or external usage. To simplify our tests, # its much simpler if we have a single kubeconfig that can be used internally and externally. # To do this, we can replace the server with the IP address of the docker container
Shell Script - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Apr 08 19:12:55 GMT 2024 - 17.3K bytes - Viewed (1) -
bin/update_crds.sh
Shell Script - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Apr 22 14:28:27 GMT 2024 - 3.4K bytes - Viewed (0)