apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-138-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-138.ec2.internal uid: 288e2a8a-b384-4695-90c7-804846951617 resourceVersion: "21539" uid: bac56f27-e5ec-494a-967c-0723dc561af8 spec: sourcePod: network-check-source-56499946bc-wtqpz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T19:33:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.003295ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:47:22Z" - latency: 1.382315ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:46:22Z" - latency: 1.190544ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:45:22Z" - latency: 889.736µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:44:22Z" - latency: 936.67µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:22Z" - latency: 1.089525ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:22Z" - latency: 926.083µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:22Z" - latency: 1.172879ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:22Z" - latency: 2.526443ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:39:22Z" - latency: 932.823µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:38:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-138-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-138.ec2.internal uid: 288e2a8a-b384-4695-90c7-804846951617 resourceVersion: "20114" uid: c61a69a8-9533-4d52-8da4-241b09c0494e spec: sourcePod: network-check-source-56499946bc-wtqpz targetEndpoint: ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T19:32:22Z" message: 'load-balancer-api-external: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.894998ms message: 'load-balancer-api-external: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:44:22Z" - latency: 9.123735ms message: 'load-balancer-api-external: resolved host name ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:44:22Z" - latency: 5.998649ms message: 'load-balancer-api-external: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:22Z" - latency: 7.810251ms message: 'load-balancer-api-external: resolved host name ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:43:22Z" - latency: 4.647379ms message: 'load-balancer-api-external: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:22Z" - latency: 7.66732ms message: 'load-balancer-api-external: resolved host name ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:42:22Z" - latency: 4.465126ms message: 'load-balancer-api-external: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:22Z" - latency: 8.146066ms message: 'load-balancer-api-external: resolved host name ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:41:22Z" - latency: 4.777005ms message: 'load-balancer-api-external: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:22Z" - latency: 9.158479ms message: 'load-balancer-api-external: resolved host name ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:40:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-138-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-138.ec2.internal uid: 288e2a8a-b384-4695-90c7-804846951617 resourceVersion: "20115" uid: aeef378e-f59e-425f-a72d-63c54c161c3e spec: sourcePod: network-check-source-56499946bc-wtqpz targetEndpoint: ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T19:32:22Z" message: 'load-balancer-api-internal: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.869485ms message: 'load-balancer-api-internal: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:44:22Z" - latency: 8.925641ms message: 'load-balancer-api-internal: resolved host name ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:44:22Z" - latency: 5.263104ms message: 'load-balancer-api-internal: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:22Z" - latency: 7.683616ms message: 'load-balancer-api-internal: resolved host name ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:43:22Z" - latency: 4.536556ms message: 'load-balancer-api-internal: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:22Z" - latency: 7.642381ms message: 'load-balancer-api-internal: resolved host name ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:42:22Z" - latency: 4.403741ms message: 'load-balancer-api-internal: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:22Z" - latency: 7.933115ms message: 'load-balancer-api-internal: resolved host name ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:41:22Z" - latency: 4.718877ms message: 'load-balancer-api-internal: tcp connection to ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:22Z" - latency: 9.090074ms message: 'load-balancer-api-internal: resolved host name ae3f795680d714125b626a06e820be79-d6c099b80010c8d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:40:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-138-to-network-check-target-ip-10-0-131-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-138.ec2.internal uid: 288e2a8a-b384-4695-90c7-804846951617 resourceVersion: "21536" uid: 98067d0c-0586-43de-bed1-6b07784375ae spec: sourcePod: network-check-source-56499946bc-wtqpz targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T19:33:22Z" message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.105661ms message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:47:22Z" - latency: 930.291µs message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:46:22Z" - latency: 902.022µs message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:45:22Z" - latency: 914.546µs message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:44:22Z" - latency: 1.158129ms message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:22Z" - latency: 749.162µs message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:22Z" - latency: 1.349167ms message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:22Z" - latency: 982.912µs message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:22Z" - latency: 1.779994ms message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:39:22Z" - latency: 1.788777ms message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:38:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-138-to-network-check-target-ip-10-0-133-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-138.ec2.internal uid: 288e2a8a-b384-4695-90c7-804846951617 resourceVersion: "21537" uid: b8078e4d-850b-42d8-aef0-f6321ab32fe2 spec: sourcePod: network-check-source-56499946bc-wtqpz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-01T19:33:22Z" message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.190348ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:47:22Z" - latency: 2.042673ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:46:22Z" - latency: 2.36562ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:45:22Z" - latency: 2.327207ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:44:22Z" - latency: 2.23411ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:22Z" - latency: 2.225608ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:22Z" - latency: 2.087066ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:22Z" - latency: 2.686465ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:22Z" - latency: 2.356078ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:39:22Z" - latency: 2.300184ms message: 'network-check-target-ip-10-0-133-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:38:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-138-to-network-check-target-ip-10-0-134-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-138.ec2.internal uid: 288e2a8a-b384-4695-90c7-804846951617 resourceVersion: "21538" uid: c004ac51-148a-44a6-993f-cbb23fc4585f spec: sourcePod: network-check-source-56499946bc-wtqpz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-01T19:33:22Z" message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.427601ms message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:47:22Z" - latency: 2.554269ms message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:46:22Z" - latency: 2.149358ms message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:45:22Z" - latency: 2.679455ms message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:44:22Z" - latency: 2.360108ms message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:22Z" - latency: 2.584837ms message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:22Z" - latency: 2.588301ms message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:22Z" - latency: 3.078041ms message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:22Z" - latency: 2.792121ms message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:39:22Z" - latency: 2.381267ms message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:38:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-138-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-138.ec2.internal uid: 288e2a8a-b384-4695-90c7-804846951617 resourceVersion: "20112" uid: fe056dc4-92a0-4660-928f-1f24b2408ebc spec: sourcePod: network-check-source-56499946bc-wtqpz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T19:32:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 832.979µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:44:22Z" - latency: 1.963338ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:44:22Z" - latency: 935.179µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:22Z" - latency: 1.718949ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:43:22Z" - latency: 723.329µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:22Z" - latency: 1.650676ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:42:22Z" - latency: 911.942µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:22Z" - latency: 1.797723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:41:22Z" - latency: 1.54254ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:22Z" - latency: 2.229705ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:40:22Z" kind: List metadata: resourceVersion: ""