apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:25:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-116-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-116.ec2.internal uid: 541b9836-defb-4d36-9a7f-dd253e17c401 resourceVersion: "51944" uid: f0638760-529e-484e-8f74-e92e82f550c9 spec: sourcePod: network-check-source-869dcfcdcd-9g2cr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T22:32:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.661996ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:00:05Z" - latency: 914.806µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:59:05Z" - latency: 877.236µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:58:05Z" - latency: 1.065528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:57:05Z" - latency: 1.350269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:56:05Z" - latency: 920.858µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:55:05Z" - latency: 1.401349ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:54:05Z" - latency: 1.417365ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:53:05Z" - latency: 879.706µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:52:05Z" - latency: 1.013192ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:51:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:25:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-116-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-116.ec2.internal uid: 541b9836-defb-4d36-9a7f-dd253e17c401 resourceVersion: "52867" uid: 60941ef4-f786-498c-a83e-8b0f5b981f7d spec: sourcePod: network-check-source-869dcfcdcd-9g2cr targetEndpoint: a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T22:31:05Z" message: 'load-balancer-api-external: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.699893ms message: 'load-balancer-api-external: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:01:05Z" - latency: 9.155006ms message: 'load-balancer-api-external: resolved host name a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:01:05Z" - latency: 4.542423ms message: 'load-balancer-api-external: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:00:05Z" - latency: 8.634737ms message: 'load-balancer-api-external: resolved host name a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:00:05Z" - latency: 4.813159ms message: 'load-balancer-api-external: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:59:05Z" - latency: 8.539269ms message: 'load-balancer-api-external: resolved host name a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T22:59:05Z" - latency: 4.388745ms message: 'load-balancer-api-external: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:58:05Z" - latency: 8.298211ms message: 'load-balancer-api-external: resolved host name a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T22:58:05Z" - latency: 4.562505ms message: 'load-balancer-api-external: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:57:05Z" - latency: 7.870671ms message: 'load-balancer-api-external: resolved host name a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T22:57:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:25:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-116-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-116.ec2.internal uid: 541b9836-defb-4d36-9a7f-dd253e17c401 resourceVersion: "52868" uid: 6b13c484-9681-47c1-baa2-66848e215e20 spec: sourcePod: network-check-source-869dcfcdcd-9g2cr targetEndpoint: a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T22:31:05Z" message: 'load-balancer-api-internal: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.96787ms message: 'load-balancer-api-internal: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:01:05Z" - latency: 9.112023ms message: 'load-balancer-api-internal: resolved host name a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:01:05Z" - latency: 4.582869ms message: 'load-balancer-api-internal: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:00:05Z" - latency: 8.588758ms message: 'load-balancer-api-internal: resolved host name a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:00:05Z" - latency: 3.882614ms message: 'load-balancer-api-internal: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:59:05Z" - latency: 8.506527ms message: 'load-balancer-api-internal: resolved host name a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T22:59:05Z" - latency: 3.275515ms message: 'load-balancer-api-internal: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:58:05Z" - latency: 8.213622ms message: 'load-balancer-api-internal: resolved host name a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T22:58:05Z" - latency: 4.948964ms message: 'load-balancer-api-internal: tcp connection to a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:57:05Z" - latency: 7.849529ms message: 'load-balancer-api-internal: resolved host name a45684a96305a40cca9927fafaae1b74-35878e4a29e5674d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T22:57:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:25:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-116-to-network-check-target-ip-10-0-132-30 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-116.ec2.internal uid: 541b9836-defb-4d36-9a7f-dd253e17c401 resourceVersion: "51942" uid: 44e5a370-8c92-4097-96c7-a9f3848840c6 spec: sourcePod: network-check-source-869dcfcdcd-9g2cr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T22:32:05Z" message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.405439ms message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:00:05Z" - latency: 2.660235ms message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:59:05Z" - latency: 2.116559ms message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:58:05Z" - latency: 2.288255ms message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:57:05Z" - latency: 2.530913ms message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:56:05Z" - latency: 2.352328ms message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:55:05Z" - latency: 2.300656ms message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:54:05Z" - latency: 2.339645ms message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:53:05Z" - latency: 2.219783ms message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:52:05Z" - latency: 2.469887ms message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:51:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:25:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-116-to-network-check-target-ip-10-0-136-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-116.ec2.internal uid: 541b9836-defb-4d36-9a7f-dd253e17c401 resourceVersion: "51943" uid: 2211e86b-25f5-457b-8394-229521a82114 spec: sourcePod: network-check-source-869dcfcdcd-9g2cr targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T22:32:05Z" message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.438094ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:00:05Z" - latency: 2.623849ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:59:05Z" - latency: 2.231089ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:58:05Z" - latency: 2.379129ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:57:05Z" - latency: 2.215653ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:56:05Z" - latency: 2.180806ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:55:05Z" - latency: 2.257864ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:54:05Z" - latency: 2.30383ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:53:05Z" - latency: 2.22121ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:52:05Z" - latency: 2.862952ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:51:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:25:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-116-to-network-check-target-ip-10-0-140-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-116.ec2.internal uid: 541b9836-defb-4d36-9a7f-dd253e17c401 resourceVersion: "51941" uid: bfa59f38-3901-4557-a9cf-60c38a844df9 spec: sourcePod: network-check-source-869dcfcdcd-9g2cr targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T22:32:05Z" message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 769.585µs message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:00:05Z" - latency: 1.120304ms message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:59:05Z" - latency: 867.942µs message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:58:05Z" - latency: 988.043µs message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:57:05Z" - latency: 1.47922ms message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:56:05Z" - latency: 843.621µs message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:55:05Z" - latency: 871.609µs message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:54:05Z" - latency: 1.494213ms message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:53:05Z" - latency: 1.183662ms message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:52:05Z" - latency: 1.286342ms message: 'network-check-target-ip-10-0-140-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:51:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:25:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-116-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-116.ec2.internal uid: 541b9836-defb-4d36-9a7f-dd253e17c401 resourceVersion: "52866" uid: 4932751e-6372-47f1-a01a-55a555834b25 spec: sourcePod: network-check-source-869dcfcdcd-9g2cr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T22:31:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.002066ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:01:05Z" - latency: 1.699237ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T23:01:05Z" - latency: 717.337µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:00:05Z" - latency: 2.211636ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T23:00:05Z" - latency: 966.366µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:59:05Z" - latency: 1.662353ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T22:59:05Z" - latency: 848.652µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:58:05Z" - latency: 2.418886ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T22:58:05Z" - latency: 875.707µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:57:05Z" - latency: 1.687671ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T22:57:05Z" kind: List metadata: resourceVersion: ""