apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:54:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-26-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-26.us-west-2.compute.internal uid: 38b2f2a6-6bf6-48fd-bc55-50324b9cbdce resourceVersion: "115177" uid: 5966e48b-8bf3-48e2-bec1-ac303a18f971 spec: sourcePod: network-check-source-6f78d59f99-xxjw5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T20:01:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.054692ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:04:14Z" - latency: 1.479308ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:03:14Z" - latency: 1.103135ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:02:14Z" - latency: 1.407447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:01:14Z" - latency: 1.343032ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:00:14Z" - latency: 1.275148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:59:14Z" - latency: 1.280605ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:58:14Z" - latency: 1.979844ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:57:14Z" - latency: 1.381065ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:56:14Z" - latency: 1.793969ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:55:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:54:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-26-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-26.us-west-2.compute.internal uid: 38b2f2a6-6bf6-48fd-bc55-50324b9cbdce resourceVersion: "116817" uid: d46eee37-67da-4d24-8ef6-0f6d68f1cbd5 spec: sourcePod: network-check-source-6f78d59f99-xxjw5 targetEndpoint: a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T20:00:14Z" message: 'load-balancer-api-external: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.989537ms message: 'load-balancer-api-external: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:06:14Z" - latency: 6.478654ms message: 'load-balancer-api-external: resolved host name a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:06:14Z" - latency: 51.526825ms message: 'load-balancer-api-external: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:05:14Z" - latency: 7.019663ms message: 'load-balancer-api-external: resolved host name a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:05:14Z" - latency: 53.766024ms message: 'load-balancer-api-external: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:04:14Z" - latency: 7.889525ms message: 'load-balancer-api-external: resolved host name a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:04:14Z" - latency: 50.215588ms message: 'load-balancer-api-external: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:03:14Z" - latency: 7.276809ms message: 'load-balancer-api-external: resolved host name a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:03:14Z" - latency: 50.954701ms message: 'load-balancer-api-external: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:02:14Z" - latency: 7.22765ms message: 'load-balancer-api-external: resolved host name a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:02:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:54:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-26-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-26.us-west-2.compute.internal uid: 38b2f2a6-6bf6-48fd-bc55-50324b9cbdce resourceVersion: "116818" uid: 90f635cb-4b72-40a8-8433-1a014fa778ba spec: sourcePod: network-check-source-6f78d59f99-xxjw5 targetEndpoint: a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T20:00:14Z" message: 'load-balancer-api-internal: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.056562ms message: 'load-balancer-api-internal: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:06:14Z" - latency: 6.49803ms message: 'load-balancer-api-internal: resolved host name a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:06:14Z" - latency: 56.448199ms message: 'load-balancer-api-internal: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:05:14Z" - latency: 7.105095ms message: 'load-balancer-api-internal: resolved host name a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:05:14Z" - latency: 50.51642ms message: 'load-balancer-api-internal: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:04:14Z" - latency: 7.939693ms message: 'load-balancer-api-internal: resolved host name a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:04:14Z" - latency: 50.300891ms message: 'load-balancer-api-internal: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:03:14Z" - latency: 7.331547ms message: 'load-balancer-api-internal: resolved host name a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:03:14Z" - latency: 50.467786ms message: 'load-balancer-api-internal: tcp connection to a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:02:14Z" - latency: 7.260274ms message: 'load-balancer-api-internal: resolved host name a83af7d525ec44176aabcd0e4302dda2-d27cf1d047af92e6.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:02:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:54:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-26-to-network-check-target-ip-10-0-130-111 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-26.us-west-2.compute.internal uid: 38b2f2a6-6bf6-48fd-bc55-50324b9cbdce resourceVersion: "115175" uid: 63eb7b03-d278-4009-8414-75582cd29f52 spec: sourcePod: network-check-source-6f78d59f99-xxjw5 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T20:01:14Z" message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.304074ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:04:14Z" - latency: 2.368431ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:03:14Z" - latency: 2.045141ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:02:14Z" - latency: 2.534074ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:01:14Z" - latency: 2.063459ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:00:14Z" - latency: 2.691788ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:59:14Z" - latency: 2.363645ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:58:14Z" - latency: 3.691428ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:57:14Z" - latency: 2.330684ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:56:14Z" - latency: 2.669908ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:55:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:54:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-26-to-network-check-target-ip-10-0-133-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-26.us-west-2.compute.internal uid: 38b2f2a6-6bf6-48fd-bc55-50324b9cbdce resourceVersion: "115174" uid: 273cb955-6048-4f0c-ab8a-0b73b9e56b70 spec: sourcePod: network-check-source-6f78d59f99-xxjw5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T20:01:14Z" message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.091062ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:04:14Z" - latency: 1.016241ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:03:14Z" - latency: 1.279494ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:02:14Z" - latency: 1.123893ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:01:14Z" - latency: 1.415144ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:00:14Z" - latency: 1.018818ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:59:14Z" - latency: 959.761µs message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:58:14Z" - latency: 2.140743ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:57:14Z" - latency: 1.155126ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:56:14Z" - latency: 1.512361ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:55:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:54:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-26-to-network-check-target-ip-10-0-134-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-26.us-west-2.compute.internal uid: 38b2f2a6-6bf6-48fd-bc55-50324b9cbdce resourceVersion: "115176" uid: a4eb690b-1158-40f5-b2fc-e040ae083701 spec: sourcePod: network-check-source-6f78d59f99-xxjw5 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T20:01:14Z" message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.672484ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:04:14Z" - latency: 2.538633ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:03:14Z" - latency: 2.364208ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:02:14Z" - latency: 2.23881ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:01:14Z" - latency: 1.996228ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:00:14Z" - latency: 2.400014ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:59:14Z" - latency: 2.700653ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:58:14Z" - latency: 3.592655ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:57:14Z" - latency: 2.075718ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:56:14Z" - latency: 2.429301ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T20:55:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:54:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-26-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-26.us-west-2.compute.internal uid: 38b2f2a6-6bf6-48fd-bc55-50324b9cbdce resourceVersion: "116816" uid: 1a859106-b450-4103-803a-563b7671c010 spec: sourcePod: network-check-source-6f78d59f99-xxjw5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T20:00:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.522084ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:06:14Z" - latency: 1.937892ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T21:06:14Z" - latency: 1.113316ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:05:14Z" - latency: 2.402742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T21:05:14Z" - latency: 1.36838ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:04:14Z" - latency: 2.249696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T21:04:14Z" - latency: 940.096µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:03:14Z" - latency: 2.140676ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T21:03:14Z" - latency: 1.181436ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:02:14Z" - latency: 2.062341ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T21:02:14Z" kind: List metadata: resourceVersion: ""