apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-215-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-215.ec2.internal uid: ef9b1205-adb7-4442-adc5-d5af2c2f3d67 resourceVersion: "44663" uid: 23604ae9-75fc-4e1c-af49-15982fc63600 spec: sourcePod: network-check-source-6947749cfc-bmwpm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T19:33:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.059726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:54:43Z" - latency: 1.043566ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:53:43Z" - latency: 1.009023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:52:43Z" - latency: 1.247815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:51:43Z" - latency: 1.204468ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:50:43Z" - latency: 1.134132ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:49:43Z" - latency: 1.129447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:48:43Z" - latency: 1.004093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:43Z" - latency: 1.151672ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:43Z" - latency: 1.108778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-215-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-215.ec2.internal uid: ef9b1205-adb7-4442-adc5-d5af2c2f3d67 resourceVersion: "46723" uid: c8721a62-641a-49d8-9c51-13b31be49db4 spec: sourcePod: network-check-source-6947749cfc-bmwpm targetEndpoint: a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T19:32:43Z" message: 'load-balancer-api-external: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.085255ms message: 'load-balancer-api-external: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:56:43Z" - latency: 8.726193ms message: 'load-balancer-api-external: resolved host name a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:56:43Z" - latency: 4.889803ms message: 'load-balancer-api-external: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:55:43Z" - latency: 8.505183ms message: 'load-balancer-api-external: resolved host name a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:55:43Z" - latency: 4.523317ms message: 'load-balancer-api-external: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:54:43Z" - latency: 9.906723ms message: 'load-balancer-api-external: resolved host name a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:54:43Z" - latency: 4.174676ms message: 'load-balancer-api-external: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:53:43Z" - latency: 8.47645ms message: 'load-balancer-api-external: resolved host name a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:53:43Z" - latency: 3.725281ms message: 'load-balancer-api-external: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:52:43Z" - latency: 9.20105ms message: 'load-balancer-api-external: resolved host name a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:52:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-215-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-215.ec2.internal uid: ef9b1205-adb7-4442-adc5-d5af2c2f3d67 resourceVersion: "46722" uid: 34768dd8-fd37-4bab-9c87-eba37e1a1bb3 spec: sourcePod: network-check-source-6947749cfc-bmwpm targetEndpoint: a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T19:32:43Z" message: 'load-balancer-api-internal: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.099327ms message: 'load-balancer-api-internal: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:56:43Z" - latency: 8.678889ms message: 'load-balancer-api-internal: resolved host name a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:56:43Z" - latency: 3.589772ms message: 'load-balancer-api-internal: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:55:43Z" - latency: 8.455621ms message: 'load-balancer-api-internal: resolved host name a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:55:43Z" - latency: 4.557025ms message: 'load-balancer-api-internal: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:54:43Z" - latency: 9.878973ms message: 'load-balancer-api-internal: resolved host name a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:54:43Z" - latency: 3.606506ms message: 'load-balancer-api-internal: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:53:43Z" - latency: 8.462508ms message: 'load-balancer-api-internal: resolved host name a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:53:43Z" - latency: 4.814566ms message: 'load-balancer-api-internal: tcp connection to a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:52:43Z" - latency: 9.21682ms message: 'load-balancer-api-internal: resolved host name a069988098f5b426c9b4aa04f0d3d9d5-835d16377cb81df5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:52:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-215-to-network-check-target-ip-10-0-130-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-215.ec2.internal uid: ef9b1205-adb7-4442-adc5-d5af2c2f3d67 resourceVersion: "44661" uid: 736f8264-5bc6-41af-9f7a-f775e14ca0ac spec: sourcePod: network-check-source-6947749cfc-bmwpm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T19:33:43Z" message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.099728ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:54:43Z" - latency: 1.300225ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:53:43Z" - latency: 968.4µs message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:52:43Z" - latency: 874.654µs message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:51:43Z" - latency: 976.506µs message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:50:43Z" - latency: 975.826µs message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:49:43Z" - latency: 899.929µs message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:48:43Z" - latency: 992.93µs message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:43Z" - latency: 856.521µs message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:43Z" - latency: 1.036143ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-215-to-network-check-target-ip-10-0-131-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-215.ec2.internal uid: ef9b1205-adb7-4442-adc5-d5af2c2f3d67 resourceVersion: "44660" uid: 1f1504e8-36ce-418d-9847-4d3da5867a2e spec: sourcePod: network-check-source-6947749cfc-bmwpm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T19:33:43Z" message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.576802ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:54:43Z" - latency: 2.377ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:53:43Z" - latency: 2.491109ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:52:43Z" - latency: 2.61053ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:51:43Z" - latency: 2.548352ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:50:43Z" - latency: 2.25225ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:49:43Z" - latency: 2.346518ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:48:43Z" - latency: 2.435463ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:43Z" - latency: 2.390023ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:43Z" - latency: 2.3839ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-215-to-network-check-target-ip-10-0-135-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-215.ec2.internal uid: ef9b1205-adb7-4442-adc5-d5af2c2f3d67 resourceVersion: "44662" uid: a5afc3db-6a58-4cd8-b3a1-f84751d97c54 spec: sourcePod: network-check-source-6947749cfc-bmwpm targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T19:33:43Z" message: 'network-check-target-ip-10-0-135-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.355846ms message: 'network-check-target-ip-10-0-135-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:54:43Z" - latency: 2.424125ms message: 'network-check-target-ip-10-0-135-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:53:43Z" - latency: 2.374208ms message: 'network-check-target-ip-10-0-135-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:52:43Z" - latency: 2.707597ms message: 'network-check-target-ip-10-0-135-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:51:43Z" - latency: 2.344742ms message: 'network-check-target-ip-10-0-135-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:50:43Z" - latency: 2.338548ms message: 'network-check-target-ip-10-0-135-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:49:43Z" - latency: 2.266858ms message: 'network-check-target-ip-10-0-135-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:48:43Z" - latency: 2.284898ms message: 'network-check-target-ip-10-0-135-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:47:43Z" - latency: 2.236146ms message: 'network-check-target-ip-10-0-135-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:46:43Z" - latency: 2.09883ms message: 'network-check-target-ip-10-0-135-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:45:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T19:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-215-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-215.ec2.internal uid: ef9b1205-adb7-4442-adc5-d5af2c2f3d67 resourceVersion: "46721" uid: 25b13b89-0c26-48c6-a7ff-c7b377fec630 spec: sourcePod: network-check-source-6947749cfc-bmwpm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T19:32:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.233022ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:56:43Z" - latency: 1.882858ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:56:43Z" - latency: 1.054145ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:55:43Z" - latency: 2.046367ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:55:43Z" - latency: 861.253µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:54:43Z" - latency: 2.693428ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:54:43Z" - latency: 929.712µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:53:43Z" - latency: 1.773257ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:53:43Z" - latency: 767.391µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:52:43Z" - latency: 1.692822ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:52:43Z" kind: List metadata: resourceVersion: ""