-
io/v1beta1",
"metadata": {
"selflink": "/apis/metrics.k8s.io/v1beta1/pods"
},
"items": [
{
"metadata": {
"name": "kube-system",
"selflink": "/apis/metrics.k8s.io/v1beta1/namespace/kube-system/pods/coredns-5644d7b6d9-rv295",
"creationTimestamp": "2019-11-06T02:40:21Z" Nodes https://K8S_API_SERVER:6443/apis/metrics.k8s.io/v1beta1/nodes Pods https://K8S_API_SERVER:6443/apis/metrics.k8s.io/v1beta1/pods
{
"kind": "PodMetricsList",
"apiVersion":
0 码力 |
25 页 |
11.98 MB
| 2 年前 3
-
can monitor as Cilium and all required components are being installed:
kubectl -n kube-system get pods --watch
NAME READY STATUS
RESTARTS AGE
cil Deploy the connectivity test
You can deploy the “connectivity-check” to test connectivity between pods. It is
recommended to create a separate namespace for this.
kubectl create ns cilium-test
Deploy variant and the readiness and liveness gate indicates success or failure
of the test:
$ kubectl get pods -n cilium-test
NAME READY STATUS
RESTARTS
0 码力 |
1263 页 |
18.62 MB
| 1 年前 3
-
Installation
Installation using Helm
Advanced Installation
Considerations on node pool taints and unmanaged pods
Observability
Setting up Hubble Observability
Inspecting Network Flows with the CLI
Service Map & export NAME="$(whoami)-$RANDOM"
# Create the node pool with the following taint to guarantee that
# Pods are only scheduled/executed in the node when Cilium is ready.
# Alternatively, see the note below Note
Please make sure to read and understand the documentation page on taint effects
and unmanaged pods.
AKS (BYOCNI)
Note
BYOCNI is the preferred way to run Cilium on AKS, however integration with the
0 码力 |
1373 页 |
19.37 MB
| 1 年前 3
-
Installation using Helm
• Advanced Installation
• Considerations on node pool taints and unmanaged pods
## Observability
• Setting up Hubble Observability.
• Inspecting Network Flows with the CLI
• NAME="$(whoami)-$RANDOM"
# Create the node pool with the following taint to guarantee that
# Pods are only scheduled/executed in the node when Cilium is ready.
# Alternatively, see the note below Note
Please make sure to read and understand the documentation page on taint effects and unmanaged pods.
AKS (BYOCNI)
## Note
BYOCNI is the preferred way to run Cilium on AKS, however integration with
0 码力 |
1307 页 |
19.26 MB
| 1 年前 3
-
can monitor as Cilium and all required components are being installed:
kubectl -n kube-system get pods --watch
NAME READY STATUS
RESTARTS AGE
cil Deploy the connectivity test
You can deploy the “connectivity-check” to test connectivity between pods. It is
recommended to create a separate namespace for this.
kubectl create ns cilium-test
Deploy variant and the readiness and liveness gate indicates success or failure
of the test:
$ kubectl get pods -n cilium-test
NAME READY STATUS
RESTARTS
0 码力 |
1124 页 |
21.33 MB
| 1 年前 3
-
can monitor as Cilium and all required components are being installed:
kubectl -n kube-system get pods --watch
NAME READY STATUS
RESTARTS AGE
cil Deploy the connectivity test
You can deploy the “connectivity-check” to test connectivity between pods.
kubectl apply -f https://raw.githubusercontent.com/cilium/cilium/v1.7/examp
It will deploy a series unmanaged Pods
If you did not use the nodeinit.restartPods=true in the Helm options when
deploying Cilium, then unmanaged pods need to be restarted manually. Restart all
already running pods which are
0 码力 |
885 页 |
12.41 MB
| 1 年前 3
-
required components are being installed:
| kubectl -n kube-system get pods --watch |
| NAME | READY | STATUS | |
| RESTARTS | pods.
kubectl apply -f https://raw.github.com/cilium/cilium/v1.6/exam
It will deploy a simple probe and readiness while it can successfully reach the echo server:
| kubectl get pods |
| NAME | READY | STATUS | RESTARTS | AGE |
0 码力 |
734 页 |
11.45 MB
| 1 年前 3 -
Corefile: |
:53 {
errors
health
kubernetes cluster.local in-addr.arpa ip6.arpa {
pods insecure
upstream
fallthrough in-addr.arpa ip6.arpa
}
prometheus :9153
proxy requires a CNI plugin to provide networking between the etcd pods forming the cluster. Cilium has special logic built in that allows etcd pods to communicate during the bootstrapping phase of Cilium.
## can monitor as Cilium and all required components are being installed:
kubectl -n kube-system get pods --watch
NAME READY STATUS RESTA
cilium-etcd-operator-6ffbd46df9-pn6cf 0 码力 |
740 页 |
12.52 MB
| 1 年前 3 -
resource. One container can have a database role, while the other can be a load-balancer. Similarly, all pods could be labeled by geography, with applied values like US, EU, APAC, etc. If done in the right manner expression matches labels to filter certain resources. For example, you may want to search for all pods that belong to a certain service, or find all containers that have a specific tier label value as uses of replication controllers is to maintain a certain number of pods. This is also useful when you want to enable certain number of pods for scaling, or ensure that at least one pod. It is a best practice 0 码力 |
66 页 |
6.10 MB
| 2 年前 3 -
3. 查看 pod
使用oc get pods命令查看当前项目的 pod。
注意
当您在 pod 中运行 oc 且没有指定命名空间时，默认使用 pod 的命名空间。
$ oc get pods -o wide
## 输出示例
create -f FILENAME [flags]
...
## - 使用oc explain命令查看特定资源的描述信息和项信息：
## 示例：查看 Pod 资源的文档
$ oc explain pods
## 输出示例
## DESCRIPTION:
FIELDS:
apiVersion
APIVersion defines the versioned schema of com/openshift/ruby-hello-world with joe-project/ruby-20-centos7:latest
#1 deployed 22 minutes ago - 2 pods
To see more information about a service or deployment, use 'oc describe service ' or 0 码力 |
120 页 |
1.04 MB
| 2 年前 3
|
Zabbix高级应用 -- K8S 集群监控io/v1beta1", "metadata": { "selflink": "/apis/metrics.k8s.io/v1beta1/pods" }, "items": [ { "metadata": { "name": "kube-system", "selflink": "/apis/metrics.k8s.io/v1beta1/namespace/kube-system/pods/coredns-5644d7b6d9-rv295", "creationTimestamp": "2019-11-06T02:40:21Z" Nodes https://K8S_API_SERVER:6443/apis/metrics.k8s.io/v1beta1/nodes Pods https://K8S_API_SERVER:6443/apis/metrics.k8s.io/v1beta1/pods { "kind": "PodMetricsList", "apiVersion":0 码力 | 25 页 | 11.98 MB | 2 年前3
Cilium v1.9 Documentationcan monitor as Cilium and all required components are being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS AGE cil Deploy the connectivity test You can deploy the “connectivity-check” to test connectivity between pods. It is recommended to create a separate namespace for this. kubectl create ns cilium-test Deploy variant and the readiness and liveness gate indicates success or failure of the test: $ kubectl get pods -n cilium-test NAME READY STATUS RESTARTS0 码力 | 1263 页 | 18.62 MB | 1 年前3