apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:49:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: bb987289-d955-4b67-b68d-dc2508d17a5f resourceVersion: "18700" uid: 5d5a2452-163f-4a25-8858-46fdbb771b66 spec: sourcePod: network-check-source-56499946bc-4bj29 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T20:56:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.873µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:03:40Z" - latency: 1.539774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:02:40Z" - latency: 1.148696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:01:40Z" - latency: 905.922µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:00:40Z" - latency: 918.359µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:59:40Z" - latency: 1.559089ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:58:40Z" - latency: 1.114907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:57:40Z" - latency: 1.364307ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:56:40Z" - latency: 884.925µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:55:40Z" - latency: 933.377µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:54:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:49:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: bb987289-d955-4b67-b68d-dc2508d17a5f resourceVersion: "20524" uid: 6f908c75-7a47-4f3c-b327-a128acf485e4 spec: sourcePod: network-check-source-56499946bc-4bj29 targetEndpoint: a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T20:55:40Z" message: 'load-balancer-api-external: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.643432ms message: 'load-balancer-api-external: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:07:40Z" - latency: 8.263888ms message: 'load-balancer-api-external: resolved host name a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T21:07:40Z" - latency: 4.698662ms message: 'load-balancer-api-external: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:06:40Z" - latency: 6.981884ms message: 'load-balancer-api-external: resolved host name a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T21:06:40Z" - latency: 5.081931ms message: 'load-balancer-api-external: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:05:40Z" - latency: 9.154203ms message: 'load-balancer-api-external: resolved host name a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T21:05:40Z" - latency: 4.819032ms message: 'load-balancer-api-external: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:04:40Z" - latency: 7.590486ms message: 'load-balancer-api-external: resolved host name a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T21:04:40Z" - latency: 5.093383ms message: 'load-balancer-api-external: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:03:40Z" - latency: 7.888071ms message: 'load-balancer-api-external: resolved host name a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T21:03:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:49:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: bb987289-d955-4b67-b68d-dc2508d17a5f resourceVersion: "20525" uid: 2e1217d6-ea33-4b84-a9ac-e360398dbd9d spec: sourcePod: network-check-source-56499946bc-4bj29 targetEndpoint: a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T20:55:40Z" message: 'load-balancer-api-internal: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.6733ms message: 'load-balancer-api-internal: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:07:40Z" - latency: 8.206773ms message: 'load-balancer-api-internal: resolved host name a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T21:07:40Z" - latency: 4.756156ms message: 'load-balancer-api-internal: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:06:40Z" - latency: 6.952067ms message: 'load-balancer-api-internal: resolved host name a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T21:06:40Z" - latency: 4.235841ms message: 'load-balancer-api-internal: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:05:40Z" - latency: 9.175418ms message: 'load-balancer-api-internal: resolved host name a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T21:05:40Z" - latency: 4.808207ms message: 'load-balancer-api-internal: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:04:40Z" - latency: 7.569294ms message: 'load-balancer-api-internal: resolved host name a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T21:04:40Z" - latency: 4.708141ms message: 'load-balancer-api-internal: tcp connection to a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:03:40Z" - latency: 7.850864ms message: 'load-balancer-api-internal: resolved host name a75a15c1d97fd42bfbf9a7f1ec60ad48-29c253c988586678.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T21:03:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:49:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-network-check-target-ip-10-0-129-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: bb987289-d955-4b67-b68d-dc2508d17a5f resourceVersion: "18697" uid: b9990f35-9264-4ed9-a724-434534e7a437 spec: sourcePod: network-check-source-56499946bc-4bj29 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T20:56:40Z" message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.706µs message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:03:40Z" - latency: 1.77483ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:02:40Z" - latency: 988.053µs message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:01:40Z" - latency: 750.313µs message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:00:40Z" - latency: 1.13902ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:59:40Z" - latency: 1.22613ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:58:40Z" - latency: 833.177µs message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:57:40Z" - latency: 1.032296ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:56:40Z" - latency: 1.003131ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:55:40Z" - latency: 1.712003ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:54:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:49:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-network-check-target-ip-10-0-129-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: bb987289-d955-4b67-b68d-dc2508d17a5f resourceVersion: "18699" uid: 3fc2c8df-ff14-4e37-94cb-c82c10b27e80 spec: sourcePod: network-check-source-56499946bc-4bj29 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T20:56:40Z" message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.186542ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:03:40Z" - latency: 2.567192ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:02:40Z" - latency: 2.29926ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:01:40Z" - latency: 2.017278ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:00:40Z" - latency: 2.104873ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:59:40Z" - latency: 1.941793ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:58:40Z" - latency: 2.265794ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:57:40Z" - latency: 1.988879ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:56:40Z" - latency: 2.181114ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:55:40Z" - latency: 3.007489ms message: 'network-check-target-ip-10-0-129-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:54:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:49:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-network-check-target-ip-10-0-130-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: bb987289-d955-4b67-b68d-dc2508d17a5f resourceVersion: "18698" uid: 76e85d65-fbeb-49a4-90af-b91d8e19f6c4 spec: sourcePod: network-check-source-56499946bc-4bj29 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T20:56:40Z" message: 'network-check-target-ip-10-0-130-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.040231ms message: 'network-check-target-ip-10-0-130-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:03:40Z" - latency: 2.29847ms message: 'network-check-target-ip-10-0-130-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:02:40Z" - latency: 2.072928ms message: 'network-check-target-ip-10-0-130-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:01:40Z" - latency: 1.732447ms message: 'network-check-target-ip-10-0-130-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:00:40Z" - latency: 1.917856ms message: 'network-check-target-ip-10-0-130-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:59:40Z" - latency: 1.837854ms message: 'network-check-target-ip-10-0-130-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:58:40Z" - latency: 1.89932ms message: 'network-check-target-ip-10-0-130-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:57:40Z" - latency: 1.704794ms message: 'network-check-target-ip-10-0-130-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:56:40Z" - latency: 1.90684ms message: 'network-check-target-ip-10-0-130-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:55:40Z" - latency: 2.333744ms message: 'network-check-target-ip-10-0-130-128: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:54:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T20:49:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: bb987289-d955-4b67-b68d-dc2508d17a5f resourceVersion: "20523" uid: c9fb6b0b-3e49-45dd-b332-0e6ac9759a51 spec: sourcePod: network-check-source-56499946bc-4bj29 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T20:55:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.104692ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:07:40Z" - latency: 2.01342ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T21:07:40Z" - latency: 863.343µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:06:40Z" - latency: 1.695653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T21:06:40Z" - latency: 885.222µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:05:40Z" - latency: 1.663852ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T21:05:40Z" - latency: 1.186512ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:04:40Z" - latency: 1.681897ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T21:04:40Z" - latency: 1.242509ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T21:03:40Z" - latency: 1.897409ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T21:03:40Z" kind: List metadata: resourceVersion: ""