- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for init (0.13 sec)
-
cni/README.md
- In ambient mode, the CNI plugin does not configure any networking, but is only responsible...
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri May 03 19:29:42 GMT 2024 - 12.3K bytes - Viewed (0) -
Makefile.core.mk
endif PROW_ARTIFACTS_BASE ?= https://gcsweb.istio.io/gcs/istio-prow include tools/proto/proto.mk .PHONY: default default: init build test .PHONY: init # Downloads envoy, based on the SHA defined in the base pilot Dockerfile init: $(TARGET_OUT)/istio_is_init init-ztunnel-rs @mkdir -p ${TARGET_OUT}/logs @mkdir -p ${TARGET_OUT}/release # I tried to make this dependent on what I thought was the appropriate
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed May 08 20:25:15 GMT 2024 - 22.5K bytes - Viewed (0) -
operator/README.md
Once the images are pushed, configure kubectl to point to your cluster and install the controller. Install the controller manifest: ```bash istioctl operator init --hub docker.io/<your-account> --tag latest kubectl create ns istio-system kubectl apply -f operator/samples/default-install.yaml ```
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sun Sep 17 08:27:52 GMT 2023 - 17.5K bytes - Viewed (0) -
common-protos/k8s.io/api/batch/v1/generated.proto
} // PodFailurePolicyOnExitCodesRequirement describes the requirement for handling // a failed pod based on its container exit codes. In particular, it lookups the // .state.terminated.exitCode for each app container and init container status, // represented by the .status.containerStatuses and .status.initContainerStatuses // fields in the Pod status, respectively. Containers completed with success
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 21.1K bytes - Viewed (0)