apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T03:14:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-211-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-211.ec2.internal uid: 51f963e1-d891-487c-8a44-d13deac8c454 resourceVersion: "53366" uid: ee58f2c5-7bb6-40e3-bac9-2f06c566bfee spec: sourcePod: network-check-source-6947749cfc-k25h6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-15T03:21:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.057546ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:49:32Z" - latency: 797.686µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:48:32Z" - latency: 1.237594ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:47:32Z" - latency: 954.22µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:46:32Z" - latency: 1.017579ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:45:32Z" - latency: 826.311µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:44:32Z" - latency: 941.122µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:43:32Z" - latency: 1.11993ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:42:32Z" - latency: 1.212991ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:41:32Z" - latency: 1.116818ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:40:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T03:14:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-211-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-211.ec2.internal uid: 51f963e1-d891-487c-8a44-d13deac8c454 resourceVersion: "54523" uid: db526377-d525-4336-8e9a-11bbf07a8762 spec: sourcePod: network-check-source-6947749cfc-k25h6 targetEndpoint: a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T03:20:32Z" message: 'load-balancer-api-external: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.291619ms message: 'load-balancer-api-external: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:50:32Z" - latency: 5.708086ms message: 'load-balancer-api-external: resolved host name a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T03:50:32Z" - latency: 5.574738ms message: 'load-balancer-api-external: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:49:32Z" - latency: 7.374337ms message: 'load-balancer-api-external: resolved host name a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T03:49:32Z" - latency: 4.869264ms message: 'load-balancer-api-external: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:48:32Z" - latency: 6.558316ms message: 'load-balancer-api-external: resolved host name a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T03:48:32Z" - latency: 4.264123ms message: 'load-balancer-api-external: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:47:32Z" - latency: 7.323326ms message: 'load-balancer-api-external: resolved host name a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T03:47:32Z" - latency: 4.154577ms message: 'load-balancer-api-external: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:46:32Z" - latency: 5.931106ms message: 'load-balancer-api-external: resolved host name a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T03:46:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T03:14:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-211-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-211.ec2.internal uid: 51f963e1-d891-487c-8a44-d13deac8c454 resourceVersion: "54522" uid: 56a51874-cb36-4140-8099-de54819760fd spec: sourcePod: network-check-source-6947749cfc-k25h6 targetEndpoint: a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T03:20:32Z" message: 'load-balancer-api-internal: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.296569ms message: 'load-balancer-api-internal: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:50:32Z" - latency: 5.67097ms message: 'load-balancer-api-internal: resolved host name a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T03:50:32Z" - latency: 5.583149ms message: 'load-balancer-api-internal: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:49:32Z" - latency: 7.303027ms message: 'load-balancer-api-internal: resolved host name a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T03:49:32Z" - latency: 2.871265ms message: 'load-balancer-api-internal: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:48:32Z" - latency: 6.567988ms message: 'load-balancer-api-internal: resolved host name a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T03:48:32Z" - latency: 3.119303ms message: 'load-balancer-api-internal: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:47:32Z" - latency: 7.197386ms message: 'load-balancer-api-internal: resolved host name a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T03:47:32Z" - latency: 4.391189ms message: 'load-balancer-api-internal: tcp connection to a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:46:32Z" - latency: 5.912306ms message: 'load-balancer-api-internal: resolved host name a05759a985d894d7aadc6268601c34d4-af022aad306f979c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T03:46:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T03:14:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-211-to-network-check-target-ip-10-0-133-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-211.ec2.internal uid: 51f963e1-d891-487c-8a44-d13deac8c454 resourceVersion: "53363" uid: 4ba3a23b-e0f7-47b8-a8aa-080a640e47fc spec: sourcePod: network-check-source-6947749cfc-k25h6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T03:21:32Z" message: 'network-check-target-ip-10-0-133-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.304884ms message: 'network-check-target-ip-10-0-133-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:49:32Z" - latency: 1.048081ms message: 'network-check-target-ip-10-0-133-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:48:32Z" - latency: 1.192424ms message: 'network-check-target-ip-10-0-133-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:47:32Z" - latency: 1.123719ms message: 'network-check-target-ip-10-0-133-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:46:32Z" - latency: 979.075µs message: 'network-check-target-ip-10-0-133-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:45:32Z" - latency: 865.859µs message: 'network-check-target-ip-10-0-133-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:44:32Z" - latency: 863.427µs message: 'network-check-target-ip-10-0-133-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:43:32Z" - latency: 1.141441ms message: 'network-check-target-ip-10-0-133-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:42:32Z" - latency: 879.792µs message: 'network-check-target-ip-10-0-133-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:41:32Z" - latency: 916.301µs message: 'network-check-target-ip-10-0-133-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:40:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T03:14:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-211-to-network-check-target-ip-10-0-139-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-211.ec2.internal uid: 51f963e1-d891-487c-8a44-d13deac8c454 resourceVersion: "53364" uid: f1b2dbf6-5110-49b5-96e3-0a69a7433186 spec: sourcePod: network-check-source-6947749cfc-k25h6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-15T03:21:32Z" message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.253873ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:49:32Z" - latency: 2.371721ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:48:32Z" - latency: 2.382885ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:47:32Z" - latency: 2.134079ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:46:32Z" - latency: 2.024894ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:45:32Z" - latency: 2.161548ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:44:32Z" - latency: 1.834961ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:43:32Z" - latency: 2.0192ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:42:32Z" - latency: 2.169534ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:41:32Z" - latency: 2.068002ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:40:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T03:14:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-211-to-network-check-target-ip-10-0-143-185 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-211.ec2.internal uid: 51f963e1-d891-487c-8a44-d13deac8c454 resourceVersion: "53365" uid: 10bdf26c-67a4-4d44-99de-f33d61d00534 spec: sourcePod: network-check-source-6947749cfc-k25h6 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T03:21:32Z" message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.139664ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:49:32Z" - latency: 1.675584ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:48:32Z" - latency: 1.598108ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:47:32Z" - latency: 1.710055ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:46:32Z" - latency: 1.842146ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:45:32Z" - latency: 1.820168ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:44:32Z" - latency: 1.955461ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:43:32Z" - latency: 2.010808ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:42:32Z" - latency: 2.065107ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:41:32Z" - latency: 2.006796ms message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:40:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T03:14:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-211-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-211.ec2.internal uid: 51f963e1-d891-487c-8a44-d13deac8c454 resourceVersion: "54521" uid: 2c7dec87-38e9-44a9-a614-f38e85b87bac spec: sourcePod: network-check-source-6947749cfc-k25h6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-15T03:20:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 812.197µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:50:32Z" - latency: 1.513943ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T03:50:32Z" - latency: 898.871µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:49:32Z" - latency: 2.235933ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T03:49:32Z" - latency: 768.554µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:48:32Z" - latency: 1.627509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T03:48:32Z" - latency: 1.004068ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:47:32Z" - latency: 1.910114ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T03:47:32Z" - latency: 861.022µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T03:46:32Z" - latency: 1.751767ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T03:46:32Z" kind: List metadata: resourceVersion: ""