apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:17:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-186-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-186.ec2.internal uid: c730a13b-8315-4953-ade8-e25ed2eec6d2 resourceVersion: "62305" uid: b992da79-7f8c-4235-8173-51fef93461c3 spec: sourcePod: network-check-source-869dcfcdcd-htjqx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T12:24:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.100532ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:59:29Z" - latency: 1.016932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:58:29Z" - latency: 863.959µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:57:29Z" - latency: 932.042µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:56:29Z" - latency: 764.315µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:55:29Z" - latency: 1.112987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:54:29Z" - latency: 914.789µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:53:29Z" - latency: 897.748µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:52:29Z" - latency: 1.293595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:51:29Z" - latency: 846.847µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:50:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:17:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-186-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-186.ec2.internal uid: c730a13b-8315-4953-ade8-e25ed2eec6d2 resourceVersion: "62307" uid: a0a0a414-7c07-47b5-b37c-b525fb41edb7 spec: sourcePod: network-check-source-869dcfcdcd-htjqx targetEndpoint: a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T12:23:30Z" message: 'load-balancer-api-external: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.69863ms message: 'load-balancer-api-external: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:59:30Z" - latency: 6.760749ms message: 'load-balancer-api-external: resolved host name a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:59:29Z" - latency: 3.581763ms message: 'load-balancer-api-external: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:58:30Z" - latency: 6.708361ms message: 'load-balancer-api-external: resolved host name a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:58:29Z" - latency: 3.927253ms message: 'load-balancer-api-external: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:57:30Z" - latency: 7.038512ms message: 'load-balancer-api-external: resolved host name a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:57:29Z" - latency: 4.338147ms message: 'load-balancer-api-external: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:56:30Z" - latency: 6.568041ms message: 'load-balancer-api-external: resolved host name a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:56:29Z" - latency: 4.278026ms message: 'load-balancer-api-external: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:55:30Z" - latency: 7.975079ms message: 'load-balancer-api-external: resolved host name a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:55:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:17:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-186-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-186.ec2.internal uid: c730a13b-8315-4953-ade8-e25ed2eec6d2 resourceVersion: "62306" uid: e56721df-a306-400b-be22-78c876751a7c spec: sourcePod: network-check-source-869dcfcdcd-htjqx targetEndpoint: a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T12:23:30Z" message: 'load-balancer-api-internal: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.679508ms message: 'load-balancer-api-internal: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:59:30Z" - latency: 6.80786ms message: 'load-balancer-api-internal: resolved host name a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:59:29Z" - latency: 3.809512ms message: 'load-balancer-api-internal: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:58:30Z" - latency: 6.655279ms message: 'load-balancer-api-internal: resolved host name a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:58:29Z" - latency: 3.449931ms message: 'load-balancer-api-internal: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:57:30Z" - latency: 7.023021ms message: 'load-balancer-api-internal: resolved host name a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:57:29Z" - latency: 2.944732ms message: 'load-balancer-api-internal: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:56:30Z" - latency: 6.528726ms message: 'load-balancer-api-internal: resolved host name a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:56:29Z" - latency: 3.113201ms message: 'load-balancer-api-internal: tcp connection to a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:55:30Z" - latency: 7.897371ms message: 'load-balancer-api-internal: resolved host name a0f95606dca1f420d871de6107119bdc-4dddecd4ea82ffe0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:55:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:17:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-186-to-network-check-target-ip-10-0-133-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-186.ec2.internal uid: c730a13b-8315-4953-ade8-e25ed2eec6d2 resourceVersion: "62301" uid: 76a9b84c-f6fc-41ae-9286-b3982a6f0ee8 spec: sourcePod: network-check-source-869dcfcdcd-htjqx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T12:24:29Z" message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 787.754µs message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:59:29Z" - latency: 911.785µs message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:58:29Z" - latency: 1.232559ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:57:29Z" - latency: 809.288µs message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:56:29Z" - latency: 769.04µs message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:55:29Z" - latency: 803.766µs message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:54:29Z" - latency: 885.911µs message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:53:29Z" - latency: 753.178µs message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:52:29Z" - latency: 1.48262ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:51:29Z" - latency: 845.007µs message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:50:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:17:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-186-to-network-check-target-ip-10-0-141-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-186.ec2.internal uid: c730a13b-8315-4953-ade8-e25ed2eec6d2 resourceVersion: "62302" uid: 1face878-7493-4a6e-be22-eea250975668 spec: sourcePod: network-check-source-869dcfcdcd-htjqx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T12:24:29Z" message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.080487ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:59:29Z" - latency: 2.304668ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:58:29Z" - latency: 2.342858ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:57:29Z" - latency: 2.179219ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:56:29Z" - latency: 2.021102ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:55:29Z" - latency: 2.438718ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:54:29Z" - latency: 2.422492ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:53:29Z" - latency: 2.675872ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:52:29Z" - latency: 2.232268ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:51:29Z" - latency: 2.824444ms message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:50:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:17:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-186-to-network-check-target-ip-10-0-142-29 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-186.ec2.internal uid: c730a13b-8315-4953-ade8-e25ed2eec6d2 resourceVersion: "62304" uid: 43418916-af9a-407c-a44c-9c9174fc90e9 spec: sourcePod: network-check-source-869dcfcdcd-htjqx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T12:24:29Z" message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.423704ms message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:59:29Z" - latency: 2.286696ms message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:58:29Z" - latency: 2.423224ms message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:57:29Z" - latency: 1.856388ms message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:56:29Z" - latency: 2.471416ms message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:55:29Z" - latency: 2.63043ms message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:54:29Z" - latency: 2.752304ms message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:53:29Z" - latency: 2.157634ms message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:52:29Z" - latency: 2.446289ms message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:51:29Z" - latency: 2.284751ms message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:50:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:17:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-186-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-186.ec2.internal uid: c730a13b-8315-4953-ade8-e25ed2eec6d2 resourceVersion: "62303" uid: 171209eb-fb1a-478e-a560-7a76403bb351 spec: sourcePod: network-check-source-869dcfcdcd-htjqx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T12:23:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 870.289µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:59:29Z" - latency: 1.609697ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T12:59:29Z" - latency: 776.193µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:58:29Z" - latency: 2.231666ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T12:58:29Z" - latency: 811.221µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:57:29Z" - latency: 1.439734ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T12:57:29Z" - latency: 828.481µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:56:29Z" - latency: 1.748086ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T12:56:29Z" - latency: 808.188µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:55:29Z" - latency: 1.685091ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T12:55:29Z" kind: List metadata: resourceVersion: ""