apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-36-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-36.ec2.internal uid: 19b30e2c-59fd-4fc0-b290-625c88d3387f resourceVersion: "47375" uid: 2e17f36d-f368-4921-8577-3f8693e35f05 spec: sourcePod: network-check-source-8894fc9bd-hwxfm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:38:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.064464ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:37Z" - latency: 1.05501ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:37Z" - latency: 1.098724ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:37Z" - latency: 865.609µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:37Z" - latency: 1.056963ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:37Z" - latency: 1.246478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:37Z" - latency: 944.071µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:37Z" - latency: 978.543µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:37Z" - latency: 1.057577ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:37Z" - latency: 903.024µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-36-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-36.ec2.internal uid: 19b30e2c-59fd-4fc0-b290-625c88d3387f resourceVersion: "47376" uid: a84119a1-b071-4778-850c-c88bd34d88f2 spec: sourcePod: network-check-source-8894fc9bd-hwxfm targetEndpoint: a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:37:37Z" message: 'load-balancer-api-external: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.231879ms message: 'load-balancer-api-external: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:37Z" - latency: 7.375479ms message: 'load-balancer-api-external: resolved host name a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:13:37Z" - latency: 3.942352ms message: 'load-balancer-api-external: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:37Z" - latency: 7.67175ms message: 'load-balancer-api-external: resolved host name a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:37Z" - latency: 4.800896ms message: 'load-balancer-api-external: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:37Z" - latency: 7.618822ms message: 'load-balancer-api-external: resolved host name a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:37Z" - latency: 3.936236ms message: 'load-balancer-api-external: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:37Z" - latency: 6.974508ms message: 'load-balancer-api-external: resolved host name a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:37Z" - latency: 4.273699ms message: 'load-balancer-api-external: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:37Z" - latency: 6.624711ms message: 'load-balancer-api-external: resolved host name a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:09:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-36-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-36.ec2.internal uid: 19b30e2c-59fd-4fc0-b290-625c88d3387f resourceVersion: "47377" uid: 9f03100f-881e-47c1-9351-d031feab5a11 spec: sourcePod: network-check-source-8894fc9bd-hwxfm targetEndpoint: a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:37:37Z" message: 'load-balancer-api-internal: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.42738ms message: 'load-balancer-api-internal: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:37Z" - latency: 7.296182ms message: 'load-balancer-api-internal: resolved host name a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:13:37Z" - latency: 3.829373ms message: 'load-balancer-api-internal: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:37Z" - latency: 7.544254ms message: 'load-balancer-api-internal: resolved host name a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:37Z" - latency: 4.816426ms message: 'load-balancer-api-internal: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:37Z" - latency: 7.653096ms message: 'load-balancer-api-internal: resolved host name a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:37Z" - latency: 3.99678ms message: 'load-balancer-api-internal: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:37Z" - latency: 6.880948ms message: 'load-balancer-api-internal: resolved host name a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:37Z" - latency: 3.51351ms message: 'load-balancer-api-internal: tcp connection to a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:37Z" - latency: 6.483885ms message: 'load-balancer-api-internal: resolved host name a01d81a2739d8439ab55f0c0fc859d34-54a3aef725acc4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:09:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-36-to-network-check-target-ip-10-0-133-36 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-36.ec2.internal uid: 19b30e2c-59fd-4fc0-b290-625c88d3387f resourceVersion: "47371" uid: 166bed87-63af-42de-91b0-43e7601527af spec: sourcePod: network-check-source-8894fc9bd-hwxfm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:38:37Z" message: 'network-check-target-ip-10-0-133-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.207µs message: 'network-check-target-ip-10-0-133-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:37Z" - latency: 907.672µs message: 'network-check-target-ip-10-0-133-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:37Z" - latency: 1.094074ms message: 'network-check-target-ip-10-0-133-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:37Z" - latency: 754.503µs message: 'network-check-target-ip-10-0-133-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:37Z" - latency: 888.974µs message: 'network-check-target-ip-10-0-133-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:37Z" - latency: 740.258µs message: 'network-check-target-ip-10-0-133-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:37Z" - latency: 729.378µs message: 'network-check-target-ip-10-0-133-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:37Z" - latency: 769.068µs message: 'network-check-target-ip-10-0-133-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:37Z" - latency: 1.557218ms message: 'network-check-target-ip-10-0-133-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:37Z" - latency: 1.236064ms message: 'network-check-target-ip-10-0-133-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-36-to-network-check-target-ip-10-0-134-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-36.ec2.internal uid: 19b30e2c-59fd-4fc0-b290-625c88d3387f resourceVersion: "47373" uid: e2c39291-b30b-4893-a1ca-199a51aa4959 spec: sourcePod: network-check-source-8894fc9bd-hwxfm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:38:37Z" message: 'network-check-target-ip-10-0-134-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.948673ms message: 'network-check-target-ip-10-0-134-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:37Z" - latency: 1.856082ms message: 'network-check-target-ip-10-0-134-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:37Z" - latency: 1.853581ms message: 'network-check-target-ip-10-0-134-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:37Z" - latency: 1.899046ms message: 'network-check-target-ip-10-0-134-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:37Z" - latency: 1.759025ms message: 'network-check-target-ip-10-0-134-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:37Z" - latency: 1.774151ms message: 'network-check-target-ip-10-0-134-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:37Z" - latency: 1.636162ms message: 'network-check-target-ip-10-0-134-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:37Z" - latency: 1.59367ms message: 'network-check-target-ip-10-0-134-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:37Z" - latency: 1.641266ms message: 'network-check-target-ip-10-0-134-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:37Z" - latency: 1.857814ms message: 'network-check-target-ip-10-0-134-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-36-to-network-check-target-ip-10-0-142-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-36.ec2.internal uid: 19b30e2c-59fd-4fc0-b290-625c88d3387f resourceVersion: "47372" uid: f0546d03-8e21-46db-b5b5-4131adbed956 spec: sourcePod: network-check-source-8894fc9bd-hwxfm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:38:37Z" message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.205536ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:37Z" - latency: 2.381528ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:37Z" - latency: 1.880986ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:37Z" - latency: 2.206227ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:37Z" - latency: 2.196433ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:37Z" - latency: 1.993848ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:37Z" - latency: 2.172532ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:37Z" - latency: 2.057694ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:37Z" - latency: 2.434801ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:37Z" - latency: 2.235103ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:04:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-36-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-36.ec2.internal uid: 19b30e2c-59fd-4fc0-b290-625c88d3387f resourceVersion: "47374" uid: 9d80f2a6-adb3-486a-add9-3e9848dc5c5d spec: sourcePod: network-check-source-8894fc9bd-hwxfm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:37:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 838.779µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:37Z" - latency: 1.698032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:13:37Z" - latency: 784.495µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:37Z" - latency: 1.628853ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:37Z" - latency: 843.861µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:37Z" - latency: 1.861067ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:37Z" - latency: 775.304µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:37Z" - latency: 1.513624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:37Z" - latency: 767.656µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:37Z" - latency: 1.678421ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:09:37Z" kind: List metadata: resourceVersion: ""