apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:41:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-108-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-108.ec2.internal uid: 815c28f5-83fa-4348-8965-b8b2d9fb1bfc resourceVersion: "30211" uid: af4d14b8-4283-4737-9572-78b4b36d0960 spec: sourcePod: network-check-source-6947749cfc-2vxw5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T18:48:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.519854ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:55:54Z" - latency: 1.182575ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:54:54Z" - latency: 823.985µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:53:54Z" - latency: 1.136741ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:52:54Z" - latency: 1.315182ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:51:54Z" - latency: 1.008043ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:50:54Z" - latency: 932.246µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:54Z" - latency: 760.614µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:48:54Z" - latency: 1.037267ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:47:54Z" - latency: 944.853µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:46:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:41:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-108-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-108.ec2.internal uid: 815c28f5-83fa-4348-8965-b8b2d9fb1bfc resourceVersion: "28937" uid: 57c28ec6-dc10-4426-87a5-14b9c15dcf0b spec: sourcePod: network-check-source-6947749cfc-2vxw5 targetEndpoint: a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T18:47:54Z" message: 'load-balancer-api-external: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.583335ms message: 'load-balancer-api-external: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:53:54Z" - latency: 7.662479ms message: 'load-balancer-api-external: resolved host name a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:53:54Z" - latency: 4.878309ms message: 'load-balancer-api-external: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:52:54Z" - latency: 8.090563ms message: 'load-balancer-api-external: resolved host name a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:52:54Z" - latency: 3.636216ms message: 'load-balancer-api-external: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:51:54Z" - latency: 6.578559ms message: 'load-balancer-api-external: resolved host name a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:51:54Z" - latency: 3.850373ms message: 'load-balancer-api-external: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:50:54Z" - latency: 7.110593ms message: 'load-balancer-api-external: resolved host name a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:50:54Z" - latency: 5.219896ms message: 'load-balancer-api-external: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:54Z" - latency: 8.188191ms message: 'load-balancer-api-external: resolved host name a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:49:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:41:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-108-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-108.ec2.internal uid: 815c28f5-83fa-4348-8965-b8b2d9fb1bfc resourceVersion: "28938" uid: 3cc7ef84-0c0f-4228-b2a6-a5678f7e8d68 spec: sourcePod: network-check-source-6947749cfc-2vxw5 targetEndpoint: a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T18:47:54Z" message: 'load-balancer-api-internal: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.595663ms message: 'load-balancer-api-internal: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:53:54Z" - latency: 7.768177ms message: 'load-balancer-api-internal: resolved host name a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:53:54Z" - latency: 4.836055ms message: 'load-balancer-api-internal: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:52:54Z" - latency: 8.219673ms message: 'load-balancer-api-internal: resolved host name a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:52:54Z" - latency: 3.671395ms message: 'load-balancer-api-internal: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:51:54Z" - latency: 6.549452ms message: 'load-balancer-api-internal: resolved host name a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:51:54Z" - latency: 3.682039ms message: 'load-balancer-api-internal: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:50:54Z" - latency: 7.172199ms message: 'load-balancer-api-internal: resolved host name a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:50:54Z" - latency: 5.245331ms message: 'load-balancer-api-internal: tcp connection to a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:54Z" - latency: 8.041663ms message: 'load-balancer-api-internal: resolved host name a119c5a3d47164995949688ba271bd6b-da765142573a1958.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:49:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:41:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-108-to-network-check-target-ip-10-0-132-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-108.ec2.internal uid: 815c28f5-83fa-4348-8965-b8b2d9fb1bfc resourceVersion: "30210" uid: d9db2db1-0fd5-4174-a7bc-fdfb83343899 spec: sourcePod: network-check-source-6947749cfc-2vxw5 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:48:54Z" message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.088094ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:55:54Z" - latency: 2.427699ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:54:54Z" - latency: 2.353304ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:53:54Z" - latency: 2.415436ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:52:54Z" - latency: 2.284134ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:51:54Z" - latency: 2.249675ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:50:54Z" - latency: 2.037592ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:54Z" - latency: 2.017415ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:48:54Z" - latency: 2.516128ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:47:54Z" - latency: 2.101362ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:46:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:41:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-108-to-network-check-target-ip-10-0-133-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-108.ec2.internal uid: 815c28f5-83fa-4348-8965-b8b2d9fb1bfc resourceVersion: "30208" uid: 9f6e57ef-a948-41ac-ad42-641c08562cc0 spec: sourcePod: network-check-source-6947749cfc-2vxw5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:48:54Z" message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.236766ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:55:54Z" - latency: 1.361196ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:54:54Z" - latency: 1.410132ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:53:54Z" - latency: 880.444µs message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:52:54Z" - latency: 1.421758ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:51:54Z" - latency: 945.791µs message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:50:54Z" - latency: 1.172654ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:54Z" - latency: 1.295148ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:48:54Z" - latency: 1.151635ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:47:54Z" - latency: 790.823µs message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:46:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:41:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-108-to-network-check-target-ip-10-0-137-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-108.ec2.internal uid: 815c28f5-83fa-4348-8965-b8b2d9fb1bfc resourceVersion: "30209" uid: bae0c951-4324-43bc-b95b-5eb9831d8baa spec: sourcePod: network-check-source-6947749cfc-2vxw5 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:48:54Z" message: 'network-check-target-ip-10-0-137-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.071813ms message: 'network-check-target-ip-10-0-137-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:55:54Z" - latency: 2.679841ms message: 'network-check-target-ip-10-0-137-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:54:54Z" - latency: 2.388011ms message: 'network-check-target-ip-10-0-137-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:53:54Z" - latency: 2.507208ms message: 'network-check-target-ip-10-0-137-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:52:54Z" - latency: 2.284439ms message: 'network-check-target-ip-10-0-137-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:51:54Z" - latency: 2.156264ms message: 'network-check-target-ip-10-0-137-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:50:54Z" - latency: 2.406365ms message: 'network-check-target-ip-10-0-137-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:54Z" - latency: 2.041543ms message: 'network-check-target-ip-10-0-137-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:48:54Z" - latency: 2.397861ms message: 'network-check-target-ip-10-0-137-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:47:54Z" - latency: 2.104648ms message: 'network-check-target-ip-10-0-137-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:46:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:41:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-108-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-108.ec2.internal uid: 815c28f5-83fa-4348-8965-b8b2d9fb1bfc resourceVersion: "28935" uid: 2d79be30-ad60-4314-92da-b7d324b1fcfa spec: sourcePod: network-check-source-6947749cfc-2vxw5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T18:47:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.005053ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:53:54Z" - latency: 2.130027ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T18:53:54Z" - latency: 888.185µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:52:54Z" - latency: 1.642816ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T18:52:54Z" - latency: 992.604µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:51:54Z" - latency: 2.144316ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T18:51:54Z" - latency: 756.559µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:50:54Z" - latency: 1.628698ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T18:50:54Z" - latency: 836.425µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:54Z" - latency: 1.844386ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T18:49:54Z" kind: List metadata: resourceVersion: ""