apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:42:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-94-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-94.ec2.internal uid: cac1bc08-225b-40a2-9d0c-d95cddd8ebfd resourceVersion: "23281" uid: 52a19364-4eb5-4e69-a69c-e0d184c21360 spec: sourcePod: network-check-source-989f8b8dc-kcxv2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T16:49:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 950.137µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:03:39Z" - latency: 1.25451ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:02:39Z" - latency: 1.080931ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:01:39Z" - latency: 1.05028ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:00:39Z" - latency: 1.176505ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:59:39Z" - latency: 1.281422ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:58:39Z" - latency: 1.122339ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:57:39Z" - latency: 994.36µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:56:39Z" - latency: 889.203µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:39Z" - latency: 1.09042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:42:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-94-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-94.ec2.internal uid: cac1bc08-225b-40a2-9d0c-d95cddd8ebfd resourceVersion: "21678" uid: e153b975-2cd6-44e3-8a41-e5159ea47b98 spec: sourcePod: network-check-source-989f8b8dc-kcxv2 targetEndpoint: a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T16:48:39Z" message: 'load-balancer-api-external: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.152697ms message: 'load-balancer-api-external: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:00:39Z" - latency: 7.147084ms message: 'load-balancer-api-external: resolved host name a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:00:39Z" - latency: 5.879399ms message: 'load-balancer-api-external: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:59:39Z" - latency: 6.927905ms message: 'load-balancer-api-external: resolved host name a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:59:39Z" - latency: 4.626192ms message: 'load-balancer-api-external: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:58:39Z" - latency: 8.56037ms message: 'load-balancer-api-external: resolved host name a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:58:39Z" - latency: 7.543965ms message: 'load-balancer-api-external: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:57:39Z" - latency: 9.221617ms message: 'load-balancer-api-external: resolved host name a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:57:39Z" - latency: 7.465041ms message: 'load-balancer-api-external: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:56:39Z" - latency: 7.741996ms message: 'load-balancer-api-external: resolved host name a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:56:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:42:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-94-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-94.ec2.internal uid: cac1bc08-225b-40a2-9d0c-d95cddd8ebfd resourceVersion: "21677" uid: e3e31483-d179-4cca-96b2-640fd345efcf spec: sourcePod: network-check-source-989f8b8dc-kcxv2 targetEndpoint: a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T16:48:39Z" message: 'load-balancer-api-internal: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.195442ms message: 'load-balancer-api-internal: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:00:39Z" - latency: 7.114201ms message: 'load-balancer-api-internal: resolved host name a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T17:00:39Z" - latency: 5.885001ms message: 'load-balancer-api-internal: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:59:39Z" - latency: 6.882825ms message: 'load-balancer-api-internal: resolved host name a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:59:39Z" - latency: 4.584881ms message: 'load-balancer-api-internal: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:58:39Z" - latency: 8.429135ms message: 'load-balancer-api-internal: resolved host name a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:58:39Z" - latency: 5.697275ms message: 'load-balancer-api-internal: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:57:39Z" - latency: 9.09559ms message: 'load-balancer-api-internal: resolved host name a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:57:39Z" - latency: 4.869967ms message: 'load-balancer-api-internal: tcp connection to a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:56:39Z" - latency: 7.683364ms message: 'load-balancer-api-internal: resolved host name a765d5e8f66844610bfe2397ba90a36e-b5811aeca30a065f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:56:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:42:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-94-to-network-check-target-ip-10-0-131-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-94.ec2.internal uid: cac1bc08-225b-40a2-9d0c-d95cddd8ebfd resourceVersion: "23280" uid: df3b9dff-0f41-4c53-8e8b-e349eb70567d spec: sourcePod: network-check-source-989f8b8dc-kcxv2 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:49:39Z" message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.393585ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:03:39Z" - latency: 2.339566ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:02:39Z" - latency: 2.214629ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:01:39Z" - latency: 2.451242ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:00:39Z" - latency: 2.297529ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:59:39Z" - latency: 2.518708ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:58:39Z" - latency: 1.986724ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:57:39Z" - latency: 2.307533ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:56:39Z" - latency: 2.454255ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:39Z" - latency: 2.373288ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:42:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-94-to-network-check-target-ip-10-0-133-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-94.ec2.internal uid: cac1bc08-225b-40a2-9d0c-d95cddd8ebfd resourceVersion: "23279" uid: 2e0f56da-6744-40fe-b519-384e9ac907a0 spec: sourcePod: network-check-source-989f8b8dc-kcxv2 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:49:39Z" message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.316723ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:03:39Z" - latency: 2.433966ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:02:39Z" - latency: 2.046703ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:01:39Z" - latency: 2.455275ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:00:39Z" - latency: 2.253676ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:59:39Z" - latency: 2.187743ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:58:39Z" - latency: 2.411085ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:57:39Z" - latency: 2.33698ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:56:39Z" - latency: 3.79817ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:39Z" - latency: 2.325617ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:42:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-94-to-network-check-target-ip-10-0-142-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-94.ec2.internal uid: cac1bc08-225b-40a2-9d0c-d95cddd8ebfd resourceVersion: "23278" uid: 6502dafb-6206-4425-a066-17726ad418ac spec: sourcePod: network-check-source-989f8b8dc-kcxv2 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:49:39Z" message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.030008ms message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:03:39Z" - latency: 1.108251ms message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:02:39Z" - latency: 1.305973ms message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:01:39Z" - latency: 952.326µs message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:00:39Z" - latency: 1.299941ms message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:59:39Z" - latency: 1.428224ms message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:58:39Z" - latency: 1.391014ms message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:57:39Z" - latency: 962.588µs message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:56:39Z" - latency: 2.669312ms message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:55:39Z" - latency: 1.026379ms message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:54:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:42:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-94-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-94.ec2.internal uid: cac1bc08-225b-40a2-9d0c-d95cddd8ebfd resourceVersion: "21676" uid: c8ea8b6e-7d97-4897-b609-2845751e65ab spec: sourcePod: network-check-source-989f8b8dc-kcxv2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T16:48:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 921.846µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T17:00:39Z" - latency: 1.733794ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T17:00:39Z" - latency: 840.9µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:59:39Z" - latency: 1.759879ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:59:39Z" - latency: 1.051869ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:58:39Z" - latency: 1.999535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:58:39Z" - latency: 792.784µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:57:39Z" - latency: 2.079936ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:57:39Z" - latency: 973.754µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:56:39Z" - latency: 2.716339ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:56:39Z" kind: List metadata: resourceVersion: ""