apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-206-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-206.ec2.internal uid: 5801574c-6068-4092-88e0-0455d540d5a0 resourceVersion: "32149" uid: 499291ea-443f-40c2-9ab2-3a74433c6c3a spec: sourcePod: network-check-source-7d88cb55d8-nb777 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T17:27:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 986.888µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:02:15Z" - latency: 1.382324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:01:15Z" - latency: 795.877µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:00:15Z" - latency: 859.89µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:59:15Z" - latency: 971.669µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:58:15Z" - latency: 993.976µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:57:15Z" - latency: 855.49µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:15Z" - latency: 1.016912ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:15Z" - latency: 916.101µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:15Z" - latency: 947.723µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-206-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-206.ec2.internal uid: 5801574c-6068-4092-88e0-0455d540d5a0 resourceVersion: "32150" uid: 5ef45d96-506f-48b3-9154-4261b0dc81fa spec: sourcePod: network-check-source-7d88cb55d8-nb777 targetEndpoint: a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:26:15Z" message: 'load-balancer-api-external: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.15476ms message: 'load-balancer-api-external: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:02:15Z" - latency: 7.878573ms message: 'load-balancer-api-external: resolved host name a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:02:15Z" - latency: 5.853232ms message: 'load-balancer-api-external: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:01:15Z" - latency: 7.870638ms message: 'load-balancer-api-external: resolved host name a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:01:15Z" - latency: 6.035015ms message: 'load-balancer-api-external: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:00:15Z" - latency: 8.784733ms message: 'load-balancer-api-external: resolved host name a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:00:15Z" - latency: 5.074372ms message: 'load-balancer-api-external: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:59:15Z" - latency: 7.97448ms message: 'load-balancer-api-external: resolved host name a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:59:15Z" - latency: 6.640208ms message: 'load-balancer-api-external: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:58:15Z" - latency: 8.145752ms message: 'load-balancer-api-external: resolved host name a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:58:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-206-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-206.ec2.internal uid: 5801574c-6068-4092-88e0-0455d540d5a0 resourceVersion: "32151" uid: a167b0fe-1f07-4395-99ed-91fabe472a00 spec: sourcePod: network-check-source-7d88cb55d8-nb777 targetEndpoint: a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:26:15Z" message: 'load-balancer-api-internal: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.408285ms message: 'load-balancer-api-internal: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:02:15Z" - latency: 7.857579ms message: 'load-balancer-api-internal: resolved host name a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:02:15Z" - latency: 6.000462ms message: 'load-balancer-api-internal: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:01:15Z" - latency: 7.901147ms message: 'load-balancer-api-internal: resolved host name a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:01:15Z" - latency: 6.079403ms message: 'load-balancer-api-internal: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:00:15Z" - latency: 8.710587ms message: 'load-balancer-api-internal: resolved host name a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:00:15Z" - latency: 11.175873ms message: 'load-balancer-api-internal: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:59:15Z" - latency: 7.897344ms message: 'load-balancer-api-internal: resolved host name a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:59:15Z" - latency: 6.606095ms message: 'load-balancer-api-internal: tcp connection to a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:58:15Z" - latency: 8.056644ms message: 'load-balancer-api-internal: resolved host name a1ff5a421d39c4db48b92620e22f184e-f15c4d89d61e7472.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:58:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-206-to-network-check-target-ip-10-0-129-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-206.ec2.internal uid: 5801574c-6068-4092-88e0-0455d540d5a0 resourceVersion: "32145" uid: 17215e88-390c-4de0-8aa9-1714f48855e9 spec: sourcePod: network-check-source-7d88cb55d8-nb777 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:27:15Z" message: 'network-check-target-ip-10-0-129-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 787.745µs message: 'network-check-target-ip-10-0-129-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:02:15Z" - latency: 778.971µs message: 'network-check-target-ip-10-0-129-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:01:15Z" - latency: 860.043µs message: 'network-check-target-ip-10-0-129-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:00:15Z" - latency: 886.412µs message: 'network-check-target-ip-10-0-129-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:59:15Z" - latency: 1.431057ms message: 'network-check-target-ip-10-0-129-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:58:15Z" - latency: 946.435µs message: 'network-check-target-ip-10-0-129-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:57:15Z" - latency: 905.792µs message: 'network-check-target-ip-10-0-129-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:15Z" - latency: 866.118µs message: 'network-check-target-ip-10-0-129-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:15Z" - latency: 883.741µs message: 'network-check-target-ip-10-0-129-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:15Z" - latency: 1.014147ms message: 'network-check-target-ip-10-0-129-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-206-to-network-check-target-ip-10-0-134-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-206.ec2.internal uid: 5801574c-6068-4092-88e0-0455d540d5a0 resourceVersion: "32146" uid: e37a5376-6795-4213-a003-c7b196c06e2c spec: sourcePod: network-check-source-7d88cb55d8-nb777 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:27:15Z" message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.504891ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:02:15Z" - latency: 2.087399ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:01:15Z" - latency: 2.08585ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:00:15Z" - latency: 2.191273ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:59:15Z" - latency: 2.281339ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:58:15Z" - latency: 2.172673ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:57:15Z" - latency: 2.393162ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:15Z" - latency: 2.418866ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:15Z" - latency: 2.233803ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:15Z" - latency: 2.357247ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-206-to-network-check-target-ip-10-0-136-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-206.ec2.internal uid: 5801574c-6068-4092-88e0-0455d540d5a0 resourceVersion: "32147" uid: 1cbee42d-9034-4eef-9c71-919ecd02661a spec: sourcePod: network-check-source-7d88cb55d8-nb777 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:27:15Z" message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.138682ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:02:15Z" - latency: 2.216209ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:01:15Z" - latency: 2.290229ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:00:15Z" - latency: 2.079354ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:59:15Z" - latency: 2.505391ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:58:15Z" - latency: 2.371269ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:57:15Z" - latency: 2.093986ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:15Z" - latency: 2.4172ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:15Z" - latency: 2.338098ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:15Z" - latency: 2.269077ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-206-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-206.ec2.internal uid: 5801574c-6068-4092-88e0-0455d540d5a0 resourceVersion: "32148" uid: fde1caf2-12a6-4b83-8585-b3dfe1c53059 spec: sourcePod: network-check-source-7d88cb55d8-nb777 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T17:26:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.209798ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:02:15Z" - latency: 1.71438ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:02:15Z" - latency: 773.269µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:01:15Z" - latency: 1.842782ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:01:15Z" - latency: 829.832µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:00:15Z" - latency: 2.001178ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:00:15Z" - latency: 818.966µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:59:15Z" - latency: 1.60526ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:59:15Z" - latency: 867.935µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:58:15Z" - latency: 1.646013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:58:15Z" kind: List metadata: resourceVersion: ""