apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-48-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-48.ec2.internal uid: a690b172-b2db-4e92-8571-0fd744284a47 resourceVersion: "43263" uid: 7eb9d59b-a42f-4306-a8c3-6ba5af36f787 spec: sourcePod: network-check-source-7f44b6dd87-f4x4s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T16:11:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.245844ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:58Z" - latency: 1.192047ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:38:58Z" - latency: 1.228807ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:37:58Z" - latency: 1.006233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:36:58Z" - latency: 1.241806ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:35:58Z" - latency: 883.456µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:34:58Z" - latency: 1.065738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:33:58Z" - latency: 1.051877ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:32:58Z" - latency: 1.150351ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:31:58Z" - latency: 1.051848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:30:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-48-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-48.ec2.internal uid: a690b172-b2db-4e92-8571-0fd744284a47 resourceVersion: "43923" uid: ac97e27e-5909-4ff9-a2c9-fb528b36c341 spec: sourcePod: network-check-source-7f44b6dd87-f4x4s targetEndpoint: a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T16:10:58Z" message: 'load-balancer-api-external: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.008799ms message: 'load-balancer-api-external: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:40:58Z" - latency: 8.426773ms message: 'load-balancer-api-external: resolved host name a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:40:58Z" - latency: 4.925116ms message: 'load-balancer-api-external: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:58Z" - latency: 7.610833ms message: 'load-balancer-api-external: resolved host name a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:39:58Z" - latency: 5.043914ms message: 'load-balancer-api-external: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:38:58Z" - latency: 7.18975ms message: 'load-balancer-api-external: resolved host name a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:38:58Z" - latency: 4.592421ms message: 'load-balancer-api-external: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:37:58Z" - latency: 6.454889ms message: 'load-balancer-api-external: resolved host name a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:37:58Z" - latency: 4.642147ms message: 'load-balancer-api-external: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:36:58Z" - latency: 9.278228ms message: 'load-balancer-api-external: resolved host name a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:36:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-48-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-48.ec2.internal uid: a690b172-b2db-4e92-8571-0fd744284a47 resourceVersion: "43924" uid: 8532d882-5c17-4f33-b3ba-cf3570315a1c spec: sourcePod: network-check-source-7f44b6dd87-f4x4s targetEndpoint: a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T16:10:58Z" message: 'load-balancer-api-internal: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.369435ms message: 'load-balancer-api-internal: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:40:58Z" - latency: 8.404556ms message: 'load-balancer-api-internal: resolved host name a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:40:58Z" - latency: 4.896515ms message: 'load-balancer-api-internal: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:58Z" - latency: 7.689452ms message: 'load-balancer-api-internal: resolved host name a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:39:58Z" - latency: 5.026882ms message: 'load-balancer-api-internal: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:38:58Z" - latency: 7.299258ms message: 'load-balancer-api-internal: resolved host name a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:38:58Z" - latency: 5.406895ms message: 'load-balancer-api-internal: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:37:58Z" - latency: 6.525944ms message: 'load-balancer-api-internal: resolved host name a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:37:58Z" - latency: 4.637311ms message: 'load-balancer-api-internal: tcp connection to a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:36:58Z" - latency: 9.222654ms message: 'load-balancer-api-internal: resolved host name a8f8c2af62bd44d46914c9243a40526a-1ab5b5db307cdab3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:36:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-48-to-network-check-target-ip-10-0-131-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-48.ec2.internal uid: a690b172-b2db-4e92-8571-0fd744284a47 resourceVersion: "43261" uid: 8f7aebee-04d4-43af-9d21-481c7edac7b0 spec: sourcePod: network-check-source-7f44b6dd87-f4x4s targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T16:11:58Z" message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.332852ms message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:58Z" - latency: 2.098398ms message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:38:58Z" - latency: 2.366206ms message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:37:58Z" - latency: 1.863314ms message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:36:58Z" - latency: 3.286071ms message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:35:58Z" - latency: 1.98354ms message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:34:58Z" - latency: 2.42679ms message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:33:58Z" - latency: 2.501094ms message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:32:58Z" - latency: 1.961543ms message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:31:58Z" - latency: 2.139621ms message: 'network-check-target-ip-10-0-131-96: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:30:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-48-to-network-check-target-ip-10-0-133-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-48.ec2.internal uid: a690b172-b2db-4e92-8571-0fd744284a47 resourceVersion: "43262" uid: 844ae3dd-cd51-462e-9824-35c8c265d0d5 spec: sourcePod: network-check-source-7f44b6dd87-f4x4s targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T16:11:58Z" message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.751585ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:58Z" - latency: 1.770045ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:38:58Z" - latency: 1.618445ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:37:58Z" - latency: 1.850161ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:36:58Z" - latency: 1.889831ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:35:58Z" - latency: 1.834706ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:34:58Z" - latency: 1.878261ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:33:58Z" - latency: 1.940364ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:32:58Z" - latency: 1.976214ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:31:58Z" - latency: 1.872445ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:30:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-48-to-network-check-target-ip-10-0-140-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-48.ec2.internal uid: a690b172-b2db-4e92-8571-0fd744284a47 resourceVersion: "43260" uid: 7b16359d-48d4-4616-8cff-29e8218345c3 spec: sourcePod: network-check-source-7f44b6dd87-f4x4s targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T16:11:58Z" message: 'network-check-target-ip-10-0-140-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.014639ms message: 'network-check-target-ip-10-0-140-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:58Z" - latency: 983.921µs message: 'network-check-target-ip-10-0-140-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:38:58Z" - latency: 791.424µs message: 'network-check-target-ip-10-0-140-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:37:58Z" - latency: 807.988µs message: 'network-check-target-ip-10-0-140-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:36:58Z" - latency: 991.045µs message: 'network-check-target-ip-10-0-140-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:35:58Z" - latency: 844.046µs message: 'network-check-target-ip-10-0-140-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:34:58Z" - latency: 827.286µs message: 'network-check-target-ip-10-0-140-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:33:58Z" - latency: 1.47067ms message: 'network-check-target-ip-10-0-140-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:32:58Z" - latency: 881.146µs message: 'network-check-target-ip-10-0-140-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:31:58Z" - latency: 945.679µs message: 'network-check-target-ip-10-0-140-48: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:30:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-48-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-48.ec2.internal uid: a690b172-b2db-4e92-8571-0fd744284a47 resourceVersion: "43922" uid: a5efd856-3458-4e15-b05a-8c575452c1e1 spec: sourcePod: network-check-source-7f44b6dd87-f4x4s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T16:10:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 805.763µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:40:58Z" - latency: 2.457118ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:40:58Z" - latency: 1.00881ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:58Z" - latency: 2.044699ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:39:58Z" - latency: 870.154µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:38:58Z" - latency: 1.852846ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:38:58Z" - latency: 967.996µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:37:58Z" - latency: 1.714879ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:37:58Z" - latency: 852.237µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:36:58Z" - latency: 1.759272ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:36:58Z" kind: List metadata: resourceVersion: ""