apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T19:49:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 685b572f-96e5-4dc2-85aa-ad850c2f8a9a resourceVersion: "30909" uid: e243a41d-2d15-4cac-872d-7df0417886bc spec: sourcePod: network-check-source-dbd9cf844-sczkh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T19:57:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.154392ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:04:00Z" - latency: 967.609µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:03:00Z" - latency: 904.689µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:02:00Z" - latency: 1.050505ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:01:00Z" - latency: 1.386861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:00:00Z" - latency: 910.687µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:59:00Z" - latency: 1.597548ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:58:00Z" - latency: 1.316493ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:57:00Z" - latency: 1.084055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:56:00Z" - latency: 1.174984ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:55:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T19:49:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 685b572f-96e5-4dc2-85aa-ad850c2f8a9a resourceVersion: "34681" uid: 7a1933e9-1fe2-4054-b0ed-69c5d721bf88 spec: sourcePod: network-check-source-dbd9cf844-sczkh targetEndpoint: a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T19:56:00Z" message: 'load-balancer-api-external: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.0649ms message: 'load-balancer-api-external: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:08:00Z" - latency: 9.196964ms message: 'load-balancer-api-external: resolved host name a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T20:08:00Z" - latency: 5.617333ms message: 'load-balancer-api-external: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:07:00Z" - latency: 14.051707ms message: 'load-balancer-api-external: resolved host name a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T20:07:00Z" - latency: 4.917078ms message: 'load-balancer-api-external: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:06:00Z" - latency: 8.643938ms message: 'load-balancer-api-external: resolved host name a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T20:06:00Z" - latency: 4.342874ms message: 'load-balancer-api-external: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:05:00Z" - latency: 7.288052ms message: 'load-balancer-api-external: resolved host name a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T20:05:00Z" - latency: 4.001155ms message: 'load-balancer-api-external: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:04:00Z" - latency: 8.281971ms message: 'load-balancer-api-external: resolved host name a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T20:04:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T19:49:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 685b572f-96e5-4dc2-85aa-ad850c2f8a9a resourceVersion: "34682" uid: 79e545a4-70f4-4e6b-8c89-9c527776f679 spec: sourcePod: network-check-source-dbd9cf844-sczkh targetEndpoint: a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T19:56:00Z" message: 'load-balancer-api-internal: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.019729ms message: 'load-balancer-api-internal: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:08:00Z" - latency: 9.228632ms message: 'load-balancer-api-internal: resolved host name a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T20:08:00Z" - latency: 5.630186ms message: 'load-balancer-api-internal: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:07:00Z" - latency: 14.227689ms message: 'load-balancer-api-internal: resolved host name a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T20:07:00Z" - latency: 4.900431ms message: 'load-balancer-api-internal: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:06:00Z" - latency: 8.680313ms message: 'load-balancer-api-internal: resolved host name a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T20:06:00Z" - latency: 4.297098ms message: 'load-balancer-api-internal: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:05:00Z" - latency: 7.337033ms message: 'load-balancer-api-internal: resolved host name a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T20:05:00Z" - latency: 4.005082ms message: 'load-balancer-api-internal: tcp connection to a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:04:00Z" - latency: 8.322682ms message: 'load-balancer-api-internal: resolved host name a31c21806c2ea43c2b2012cd114da9ed-db3233fe1e04b853.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T20:04:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T19:49:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-network-check-target-ip-10-0-130-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 685b572f-96e5-4dc2-85aa-ad850c2f8a9a resourceVersion: "30905" uid: e346d93a-8d0b-4361-a212-b802e5b7233a spec: sourcePod: network-check-source-dbd9cf844-sczkh targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T19:57:00Z" message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.114µs message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:04:00Z" - latency: 869.969µs message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:03:00Z" - latency: 895.021µs message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:02:00Z" - latency: 1.216369ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:01:00Z" - latency: 1.043941ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:00:00Z" - latency: 985.055µs message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:59:00Z" - latency: 1.234165ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:58:00Z" - latency: 1.222143ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:57:00Z" - latency: 913.56µs message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:56:00Z" - latency: 1.04305ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:55:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T19:49:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-network-check-target-ip-10-0-136-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 685b572f-96e5-4dc2-85aa-ad850c2f8a9a resourceVersion: "30906" uid: f1804451-2142-4e0c-a573-6eab28ffbad5 spec: sourcePod: network-check-source-dbd9cf844-sczkh targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T19:57:00Z" message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.762051ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:04:00Z" - latency: 1.92239ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:03:00Z" - latency: 1.692865ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:02:00Z" - latency: 1.79045ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:01:00Z" - latency: 1.870465ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:00:00Z" - latency: 1.711534ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:59:00Z" - latency: 2.289297ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:58:00Z" - latency: 1.726411ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:57:00Z" - latency: 1.837233ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:56:00Z" - latency: 2.807387ms message: 'network-check-target-ip-10-0-136-24: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:55:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T19:49:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-network-check-target-ip-10-0-140-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 685b572f-96e5-4dc2-85aa-ad850c2f8a9a resourceVersion: "30907" uid: fdb51f7a-17e3-41c4-af7c-1e56c062248a spec: sourcePod: network-check-source-dbd9cf844-sczkh targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T19:57:00Z" message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.319373ms message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:04:00Z" - latency: 2.350392ms message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:03:00Z" - latency: 2.049655ms message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:02:00Z" - latency: 2.285003ms message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:01:00Z" - latency: 2.247724ms message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:00:00Z" - latency: 2.248173ms message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:59:00Z" - latency: 2.151853ms message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:58:00Z" - latency: 2.333205ms message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:57:00Z" - latency: 2.228217ms message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:56:00Z" - latency: 2.371128ms message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T19:55:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T19:49:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 685b572f-96e5-4dc2-85aa-ad850c2f8a9a resourceVersion: "34680" uid: 4a07617e-e116-4fa9-8859-9fbebcffb4fb spec: sourcePod: network-check-source-dbd9cf844-sczkh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T19:56:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 968.645µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:08:00Z" - latency: 1.69876ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T20:08:00Z" - latency: 877.481µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:07:00Z" - latency: 2.291914ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T20:07:00Z" - latency: 900.158µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:06:00Z" - latency: 1.949742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T20:06:00Z" - latency: 892.875µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:05:00Z" - latency: 1.708899ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T20:05:00Z" - latency: 749.021µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T20:04:00Z" - latency: 1.710068ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T20:04:00Z" kind: List metadata: resourceVersion: ""