apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T09:11:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.ec2.internal uid: e6637a63-75d3-4308-be26-4b21c1d517da resourceVersion: "54646" uid: a4ca0c66-7fe6-4898-9d70-7bfc4d67f39d spec: sourcePod: network-check-source-989f8b8dc-j8chf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T09:18:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.293336ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:46:59Z" - latency: 808.97µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:45:59Z" - latency: 863.717µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:44:59Z" - latency: 1.044699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:43:59Z" - latency: 1.31242ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:42:59Z" - latency: 800.259µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:41:59Z" - latency: 903.346µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:40:59Z" - latency: 1.651604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:39:59Z" - latency: 1.086285ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:38:59Z" - latency: 929.357µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:37:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T09:11:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.ec2.internal uid: e6637a63-75d3-4308-be26-4b21c1d517da resourceVersion: "55776" uid: bc5a1005-aa2d-4594-bf77-94b1610aecc2 spec: sourcePod: network-check-source-989f8b8dc-j8chf targetEndpoint: ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T09:17:59Z" message: 'load-balancer-api-external: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.753497ms message: 'load-balancer-api-external: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:47:59Z" - latency: 8.051654ms message: 'load-balancer-api-external: resolved host name ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T09:47:59Z" - latency: 5.233942ms message: 'load-balancer-api-external: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:46:59Z" - latency: 7.419052ms message: 'load-balancer-api-external: resolved host name ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T09:46:59Z" - latency: 3.194757ms message: 'load-balancer-api-external: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:45:59Z" - latency: 8.151162ms message: 'load-balancer-api-external: resolved host name ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T09:45:59Z" - latency: 7.408689ms message: 'load-balancer-api-external: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:44:59Z" - latency: 6.637014ms message: 'load-balancer-api-external: resolved host name ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T09:44:59Z" - latency: 6.511172ms message: 'load-balancer-api-external: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:43:59Z" - latency: 8.679013ms message: 'load-balancer-api-external: resolved host name ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T09:43:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T09:11:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.ec2.internal uid: e6637a63-75d3-4308-be26-4b21c1d517da resourceVersion: "55777" uid: 2a65cb3e-1a7b-423b-a994-367668e635cf spec: sourcePod: network-check-source-989f8b8dc-j8chf targetEndpoint: ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T09:17:59Z" message: 'load-balancer-api-internal: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.654524ms message: 'load-balancer-api-internal: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:47:59Z" - latency: 8.091351ms message: 'load-balancer-api-internal: resolved host name ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T09:47:59Z" - latency: 5.155693ms message: 'load-balancer-api-internal: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:46:59Z" - latency: 7.449304ms message: 'load-balancer-api-internal: resolved host name ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T09:46:59Z" - latency: 5.609714ms message: 'load-balancer-api-internal: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:45:59Z" - latency: 8.103174ms message: 'load-balancer-api-internal: resolved host name ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T09:45:59Z" - latency: 6.817739ms message: 'load-balancer-api-internal: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:44:59Z" - latency: 6.692705ms message: 'load-balancer-api-internal: resolved host name ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T09:44:59Z" - latency: 6.518953ms message: 'load-balancer-api-internal: tcp connection to ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:43:59Z" - latency: 8.756107ms message: 'load-balancer-api-internal: resolved host name ab2b3770847554367a9d0d96623f9d55-823ec050f261bb6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T09:43:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T09:11:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-network-check-target-ip-10-0-135-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.ec2.internal uid: e6637a63-75d3-4308-be26-4b21c1d517da resourceVersion: "54643" uid: 554ec926-1875-4065-bb6d-255b3b443607 spec: sourcePod: network-check-source-989f8b8dc-j8chf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T09:18:59Z" message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 945.741µs message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:46:59Z" - latency: 998.71µs message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:45:59Z" - latency: 935.37µs message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:44:59Z" - latency: 750.687µs message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:43:59Z" - latency: 1.392444ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:42:59Z" - latency: 1.035237ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:41:59Z" - latency: 780.106µs message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:40:59Z" - latency: 895.389µs message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:39:59Z" - latency: 879.954µs message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:38:59Z" - latency: 792.823µs message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:37:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T09:11:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-network-check-target-ip-10-0-136-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.ec2.internal uid: e6637a63-75d3-4308-be26-4b21c1d517da resourceVersion: "54644" uid: 2d9c9300-ea7a-4e32-997a-6e3934535599 spec: sourcePod: network-check-source-989f8b8dc-j8chf targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T09:18:59Z" message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.331571ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:46:59Z" - latency: 2.288482ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:45:59Z" - latency: 1.986641ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:44:59Z" - latency: 2.175733ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:43:59Z" - latency: 2.245798ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:42:59Z" - latency: 2.0135ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:41:59Z" - latency: 1.9695ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:40:59Z" - latency: 1.779683ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:39:59Z" - latency: 2.1888ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:38:59Z" - latency: 2.286362ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:37:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T09:11:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-network-check-target-ip-10-0-140-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.ec2.internal uid: e6637a63-75d3-4308-be26-4b21c1d517da resourceVersion: "54645" uid: 5ccf214a-6057-485d-9501-f7538043fa36 spec: sourcePod: network-check-source-989f8b8dc-j8chf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T09:18:59Z" message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.194062ms message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:46:59Z" - latency: 2.180648ms message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:45:59Z" - latency: 1.792296ms message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:44:59Z" - latency: 2.173499ms message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:43:59Z" - latency: 1.897589ms message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:42:59Z" - latency: 2.078187ms message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:41:59Z" - latency: 1.742191ms message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:40:59Z" - latency: 1.7302ms message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:39:59Z" - latency: 1.718644ms message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:38:59Z" - latency: 2.179108ms message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:37:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T09:11:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.ec2.internal uid: e6637a63-75d3-4308-be26-4b21c1d517da resourceVersion: "55775" uid: 703a85f6-ecf9-424e-b967-b1a2b1705bd3 spec: sourcePod: network-check-source-989f8b8dc-j8chf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T09:17:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.40323ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:47:59Z" - latency: 1.688984ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T09:47:59Z" - latency: 878.731µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:46:59Z" - latency: 1.797676ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T09:46:59Z" - latency: 834.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:45:59Z" - latency: 1.688093ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T09:45:59Z" - latency: 925.306µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:44:59Z" - latency: 1.91462ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T09:44:59Z" - latency: 1.200808ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T09:43:59Z" - latency: 1.746818ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T09:43:59Z" kind: List metadata: resourceVersion: ""