apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e2a1b972-7083-4172-bfb1-a9b7fbfaa427 resourceVersion: "55752" uid: 5eff1ec1-10fa-4cac-b33a-15d5dd505e66 spec: sourcePod: network-check-source-56499946bc-7kblg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T17:07:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 843.737µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:56Z" - latency: 830.355µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:56Z" - latency: 843.044µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:56Z" - latency: 1.205725ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:32:56Z" - latency: 1.124869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:31:56Z" - latency: 960.376µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:30:56Z" - latency: 767.516µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:29:56Z" - latency: 1.044942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:28:56Z" - latency: 1.09348ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:27:56Z" - latency: 988.213µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:26:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e2a1b972-7083-4172-bfb1-a9b7fbfaa427 resourceVersion: "56688" uid: 3731b99b-8f54-449b-add8-dd3bba8960be spec: sourcePod: network-check-source-56499946bc-7kblg targetEndpoint: a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T17:06:56Z" message: 'load-balancer-api-external: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.363735ms message: 'load-balancer-api-external: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:36:56Z" - latency: 8.195042ms message: 'load-balancer-api-external: resolved host name a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:36:56Z" - latency: 4.981832ms message: 'load-balancer-api-external: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:56Z" - latency: 7.103473ms message: 'load-balancer-api-external: resolved host name a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:35:56Z" - latency: 4.35886ms message: 'load-balancer-api-external: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:56Z" - latency: 6.040874ms message: 'load-balancer-api-external: resolved host name a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:34:56Z" - latency: 3.775616ms message: 'load-balancer-api-external: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:56Z" - latency: 7.478284ms message: 'load-balancer-api-external: resolved host name a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:33:56Z" - latency: 4.362235ms message: 'load-balancer-api-external: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:32:56Z" - latency: 6.646644ms message: 'load-balancer-api-external: resolved host name a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:32:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e2a1b972-7083-4172-bfb1-a9b7fbfaa427 resourceVersion: "56689" uid: 118b37e7-07a2-473b-8be1-41f7b5413b8b spec: sourcePod: network-check-source-56499946bc-7kblg targetEndpoint: a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T17:06:56Z" message: 'load-balancer-api-internal: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.980212ms message: 'load-balancer-api-internal: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:36:56Z" - latency: 8.0879ms message: 'load-balancer-api-internal: resolved host name a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:36:56Z" - latency: 4.044107ms message: 'load-balancer-api-internal: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:56Z" - latency: 7.019793ms message: 'load-balancer-api-internal: resolved host name a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:35:56Z" - latency: 4.728134ms message: 'load-balancer-api-internal: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:56Z" - latency: 6.074873ms message: 'load-balancer-api-internal: resolved host name a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:34:56Z" - latency: 3.770821ms message: 'load-balancer-api-internal: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:56Z" - latency: 7.391185ms message: 'load-balancer-api-internal: resolved host name a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:33:56Z" - latency: 3.6889ms message: 'load-balancer-api-internal: tcp connection to a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:32:56Z" - latency: 6.679791ms message: 'load-balancer-api-internal: resolved host name a69437dd2e5fe4f0e91932b559505f8e-0ed7593d92488bfe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:32:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-ip-10-0-129-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e2a1b972-7083-4172-bfb1-a9b7fbfaa427 resourceVersion: "55749" uid: 9bcfaf3a-8ebc-4426-ac49-92a4792c205b spec: sourcePod: network-check-source-56499946bc-7kblg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T17:07:56Z" message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 850.985µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:56Z" - latency: 1.075134ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:56Z" - latency: 824.154µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:56Z" - latency: 834.636µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:32:56Z" - latency: 2.12317ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:31:56Z" - latency: 1.522554ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:30:56Z" - latency: 948.203µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:29:56Z" - latency: 1.354481ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:28:56Z" - latency: 1.137122ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:27:56Z" - latency: 895.677µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:26:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-ip-10-0-130-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e2a1b972-7083-4172-bfb1-a9b7fbfaa427 resourceVersion: "55750" uid: 22cd62fb-39fd-4530-b363-92de769163e4 spec: sourcePod: network-check-source-56499946bc-7kblg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T17:07:56Z" message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.9618ms message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:56Z" - latency: 1.96561ms message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:56Z" - latency: 2.031657ms message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:56Z" - latency: 2.081372ms message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:32:56Z" - latency: 2.010851ms message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:31:56Z" - latency: 2.029937ms message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:30:56Z" - latency: 1.929314ms message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:29:56Z" - latency: 2.138259ms message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:28:56Z" - latency: 1.935022ms message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:27:56Z" - latency: 2.017618ms message: 'network-check-target-ip-10-0-130-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:26:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-ip-10-0-130-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e2a1b972-7083-4172-bfb1-a9b7fbfaa427 resourceVersion: "55751" uid: f80d442d-f670-4f3c-ac2c-a80c914af46c spec: sourcePod: network-check-source-56499946bc-7kblg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T17:07:56Z" message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.369089ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:56Z" - latency: 2.254582ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:56Z" - latency: 2.076807ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:56Z" - latency: 2.107228ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:32:56Z" - latency: 2.103984ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:31:56Z" - latency: 2.426698ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:30:56Z" - latency: 2.605252ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:29:56Z" - latency: 2.430961ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:28:56Z" - latency: 2.574662ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:27:56Z" - latency: 2.275873ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:26:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e2a1b972-7083-4172-bfb1-a9b7fbfaa427 resourceVersion: "56687" uid: 560bd321-e369-4291-a640-fd58935144f9 spec: sourcePod: network-check-source-56499946bc-7kblg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T17:06:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.004597ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:36:56Z" - latency: 1.6683ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:36:56Z" - latency: 935.319µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:56Z" - latency: 1.814274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:35:56Z" - latency: 945.902µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:56Z" - latency: 1.606747ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:34:56Z" - latency: 1.003963ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:56Z" - latency: 1.524528ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:33:56Z" - latency: 1.119028ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:32:56Z" - latency: 1.940955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:32:56Z" kind: List metadata: resourceVersion: ""