apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T12:45:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-58-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-58.ec2.internal uid: c738fbd4-a70a-44e8-934f-a1f3b62858f4 resourceVersion: "28867" uid: 6299e190-09ef-4831-89d4-1142271b0f0a spec: sourcePod: network-check-source-dbd9cf844-2zpgz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T12:52:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 990.019µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:59:23Z" - latency: 994.778µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:58:23Z" - latency: 911.185µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:57:23Z" - latency: 954.255µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:56:23Z" - latency: 1.017307ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:55:23Z" - latency: 1.047494ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:54:23Z" - latency: 744.302µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:53:23Z" - latency: 744.762µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:52:23Z" - latency: 902.807µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:51:23Z" - latency: 1.099433ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T12:45:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-58-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-58.ec2.internal uid: c738fbd4-a70a-44e8-934f-a1f3b62858f4 resourceVersion: "27591" uid: 5890f941-25b2-44a8-9a3b-3e2e398e547e spec: sourcePod: network-check-source-dbd9cf844-2zpgz targetEndpoint: a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T12:51:23Z" message: 'load-balancer-api-external: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.827513ms message: 'load-balancer-api-external: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:57:23Z" - latency: 7.302484ms message: 'load-balancer-api-external: resolved host name a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:57:23Z" - latency: 3.83661ms message: 'load-balancer-api-external: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:56:23Z" - latency: 8.386826ms message: 'load-balancer-api-external: resolved host name a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:56:23Z" - latency: 4.635675ms message: 'load-balancer-api-external: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:55:23Z" - latency: 6.593449ms message: 'load-balancer-api-external: resolved host name a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:55:23Z" - latency: 5.710443ms message: 'load-balancer-api-external: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:54:23Z" - latency: 7.486611ms message: 'load-balancer-api-external: resolved host name a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:54:23Z" - latency: 3.582912ms message: 'load-balancer-api-external: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:53:23Z" - latency: 8.020715ms message: 'load-balancer-api-external: resolved host name a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:53:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T12:45:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-58-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-58.ec2.internal uid: c738fbd4-a70a-44e8-934f-a1f3b62858f4 resourceVersion: "27590" uid: 64251381-4af3-43e3-9f9f-b45e6a8c4cb8 spec: sourcePod: network-check-source-dbd9cf844-2zpgz targetEndpoint: a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T12:51:23Z" message: 'load-balancer-api-internal: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.831526ms message: 'load-balancer-api-internal: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:57:23Z" - latency: 7.285798ms message: 'load-balancer-api-internal: resolved host name a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:57:23Z" - latency: 3.797794ms message: 'load-balancer-api-internal: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:56:23Z" - latency: 8.408726ms message: 'load-balancer-api-internal: resolved host name a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:56:23Z" - latency: 4.610432ms message: 'load-balancer-api-internal: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:55:23Z" - latency: 6.674801ms message: 'load-balancer-api-internal: resolved host name a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:55:23Z" - latency: 5.634785ms message: 'load-balancer-api-internal: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:54:23Z" - latency: 7.432414ms message: 'load-balancer-api-internal: resolved host name a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:54:23Z" - latency: 4.654255ms message: 'load-balancer-api-internal: tcp connection to a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:53:23Z" - latency: 7.99749ms message: 'load-balancer-api-internal: resolved host name a6a2d0084585c4a9faafe6b1d6e8507c-20829a99dd4b3d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:53:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T12:45:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-58-to-network-check-target-ip-10-0-133-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-58.ec2.internal uid: c738fbd4-a70a-44e8-934f-a1f3b62858f4 resourceVersion: "28865" uid: 0b5e95e7-66e9-49de-a68a-c66fc139f8b3 spec: sourcePod: network-check-source-dbd9cf844-2zpgz targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T12:52:23Z" message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.091725ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:59:23Z" - latency: 2.282618ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:58:23Z" - latency: 2.351602ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:57:23Z" - latency: 2.292456ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:56:23Z" - latency: 2.041869ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:55:23Z" - latency: 1.991956ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:54:23Z" - latency: 2.079322ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:53:23Z" - latency: 2.00783ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:52:23Z" - latency: 2.053445ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:51:23Z" - latency: 2.166731ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T12:45:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-58-to-network-check-target-ip-10-0-136-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-58.ec2.internal uid: c738fbd4-a70a-44e8-934f-a1f3b62858f4 resourceVersion: "28864" uid: b24b611a-071f-42ae-87bf-4c4bfc3fffd3 spec: sourcePod: network-check-source-dbd9cf844-2zpgz targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T12:52:23Z" message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.073852ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:59:23Z" - latency: 993.599µs message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:58:23Z" - latency: 1.231855ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:57:23Z" - latency: 845.408µs message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:56:23Z" - latency: 939.742µs message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:55:23Z" - latency: 1.417943ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:54:23Z" - latency: 813.736µs message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:53:23Z" - latency: 826.046µs message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:52:23Z" - latency: 812.706µs message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:51:23Z" - latency: 861.441µs message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T12:45:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-58-to-network-check-target-ip-10-0-141-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-58.ec2.internal uid: c738fbd4-a70a-44e8-934f-a1f3b62858f4 resourceVersion: "28866" uid: b5032d88-0935-4b26-8480-059665fcbf11 spec: sourcePod: network-check-source-dbd9cf844-2zpgz targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T12:52:23Z" message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.180135ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:59:23Z" - latency: 2.01199ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:58:23Z" - latency: 2.776479ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:57:23Z" - latency: 2.386534ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:56:23Z" - latency: 2.586135ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:55:23Z" - latency: 2.355879ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:54:23Z" - latency: 2.404893ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:53:23Z" - latency: 2.458906ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:52:23Z" - latency: 1.943443ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:51:23Z" - latency: 1.974884ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T12:45:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-58-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-58.ec2.internal uid: c738fbd4-a70a-44e8-934f-a1f3b62858f4 resourceVersion: "27589" uid: d240df48-1bb6-41db-ad0f-f7e36b1efb85 spec: sourcePod: network-check-source-dbd9cf844-2zpgz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T12:51:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.059888ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:57:23Z" - latency: 1.601591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T12:57:23Z" - latency: 995.766µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:56:23Z" - latency: 1.7254ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T12:56:23Z" - latency: 988.072µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:55:23Z" - latency: 1.99884ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T12:55:23Z" - latency: 968.293µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:54:23Z" - latency: 2.356436ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T12:54:23Z" - latency: 796.489µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:53:23Z" - latency: 1.608746ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T12:53:23Z" kind: List metadata: resourceVersion: ""