apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T07:41:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-15-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-15.ec2.internal uid: 2670696d-4425-4c0b-8a8d-928add626e8f resourceVersion: "44027" uid: 8e9d4dc4-5bcd-4992-8657-380cebec2a9a spec: sourcePod: network-check-source-7f44b6dd87-lszj6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T07:48:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.394531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:09:35Z" - latency: 1.030749ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:08:35Z" - latency: 1.117723ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:07:35Z" - latency: 763.238µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:06:35Z" - latency: 1.007144ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:05:35Z" - latency: 1.083885ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:04:35Z" - latency: 1.135707ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:03:35Z" - latency: 855.477µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:02:35Z" - latency: 987.066µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:01:35Z" - latency: 1.02621ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:00:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T07:41:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-15-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-15.ec2.internal uid: 2670696d-4425-4c0b-8a8d-928add626e8f resourceVersion: "46192" uid: ba19f65d-b6d9-419d-8523-286d39736859 spec: sourcePod: network-check-source-7f44b6dd87-lszj6 targetEndpoint: a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T07:47:35Z" message: 'load-balancer-api-external: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.767194ms message: 'load-balancer-api-external: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:11:35Z" - latency: 7.762196ms message: 'load-balancer-api-external: resolved host name a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T08:11:35Z" - latency: 5.464928ms message: 'load-balancer-api-external: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:10:35Z" - latency: 7.694477ms message: 'load-balancer-api-external: resolved host name a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T08:10:35Z" - latency: 4.448741ms message: 'load-balancer-api-external: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:09:35Z" - latency: 7.987791ms message: 'load-balancer-api-external: resolved host name a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T08:09:35Z" - latency: 3.717208ms message: 'load-balancer-api-external: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:08:35Z" - latency: 8.403914ms message: 'load-balancer-api-external: resolved host name a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T08:08:35Z" - latency: 4.424343ms message: 'load-balancer-api-external: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:07:35Z" - latency: 8.391937ms message: 'load-balancer-api-external: resolved host name a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T08:07:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T07:41:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-15-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-15.ec2.internal uid: 2670696d-4425-4c0b-8a8d-928add626e8f resourceVersion: "46191" uid: f4256bc9-6ac6-419f-baf6-68c470d5742a spec: sourcePod: network-check-source-7f44b6dd87-lszj6 targetEndpoint: a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T07:47:35Z" message: 'load-balancer-api-internal: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.825695ms message: 'load-balancer-api-internal: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:11:35Z" - latency: 7.716515ms message: 'load-balancer-api-internal: resolved host name a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T08:11:35Z" - latency: 5.251793ms message: 'load-balancer-api-internal: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:10:35Z" - latency: 7.656667ms message: 'load-balancer-api-internal: resolved host name a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T08:10:35Z" - latency: 4.455978ms message: 'load-balancer-api-internal: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:09:35Z" - latency: 8.066555ms message: 'load-balancer-api-internal: resolved host name a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T08:09:35Z" - latency: 3.688786ms message: 'load-balancer-api-internal: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:08:35Z" - latency: 8.471028ms message: 'load-balancer-api-internal: resolved host name a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T08:08:35Z" - latency: 5.062162ms message: 'load-balancer-api-internal: tcp connection to a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:07:35Z" - latency: 8.507887ms message: 'load-balancer-api-internal: resolved host name a95ac85a95b044fc2a268c1146784b09-ffb4321eb662911e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T08:07:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T07:41:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-15-to-network-check-target-ip-10-0-133-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-15.ec2.internal uid: 2670696d-4425-4c0b-8a8d-928add626e8f resourceVersion: "44024" uid: 358e4775-5777-462c-a375-a6d880eba957 spec: sourcePod: network-check-source-7f44b6dd87-lszj6 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T07:48:35Z" message: 'network-check-target-ip-10-0-133-15: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.023397ms message: 'network-check-target-ip-10-0-133-15: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:09:35Z" - latency: 838.098µs message: 'network-check-target-ip-10-0-133-15: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:08:35Z" - latency: 1.292635ms message: 'network-check-target-ip-10-0-133-15: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:07:35Z" - latency: 871.891µs message: 'network-check-target-ip-10-0-133-15: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:06:35Z" - latency: 813.197µs message: 'network-check-target-ip-10-0-133-15: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:05:35Z" - latency: 738.665µs message: 'network-check-target-ip-10-0-133-15: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:04:35Z" - latency: 934.15µs message: 'network-check-target-ip-10-0-133-15: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:03:35Z" - latency: 920.446µs message: 'network-check-target-ip-10-0-133-15: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:02:35Z" - latency: 951.213µs message: 'network-check-target-ip-10-0-133-15: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:01:35Z" - latency: 1.543404ms message: 'network-check-target-ip-10-0-133-15: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:00:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T07:41:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-15-to-network-check-target-ip-10-0-133-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-15.ec2.internal uid: 2670696d-4425-4c0b-8a8d-928add626e8f resourceVersion: "44026" uid: 06aec066-eb1c-45d1-914c-8671b482c148 spec: sourcePod: network-check-source-7f44b6dd87-lszj6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-25T07:48:35Z" message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.121278ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:09:35Z" - latency: 2.084588ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:08:35Z" - latency: 2.193478ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:07:35Z" - latency: 1.981765ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:06:35Z" - latency: 2.222952ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:05:35Z" - latency: 2.169585ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:04:35Z" - latency: 2.33288ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:03:35Z" - latency: 2.250977ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:02:35Z" - latency: 1.963055ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:01:35Z" - latency: 2.112664ms message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:00:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T07:41:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-15-to-network-check-target-ip-10-0-134-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-15.ec2.internal uid: 2670696d-4425-4c0b-8a8d-928add626e8f resourceVersion: "44025" uid: adf268c3-254d-47a2-9631-a8c96040763d spec: sourcePod: network-check-source-7f44b6dd87-lszj6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T07:48:35Z" message: 'network-check-target-ip-10-0-134-2: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.38304ms message: 'network-check-target-ip-10-0-134-2: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:09:35Z" - latency: 2.242441ms message: 'network-check-target-ip-10-0-134-2: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:08:35Z" - latency: 2.239731ms message: 'network-check-target-ip-10-0-134-2: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:07:35Z" - latency: 2.324581ms message: 'network-check-target-ip-10-0-134-2: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:06:35Z" - latency: 2.081245ms message: 'network-check-target-ip-10-0-134-2: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:05:35Z" - latency: 2.24834ms message: 'network-check-target-ip-10-0-134-2: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:04:35Z" - latency: 2.341745ms message: 'network-check-target-ip-10-0-134-2: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:03:35Z" - latency: 2.272974ms message: 'network-check-target-ip-10-0-134-2: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:02:35Z" - latency: 1.980617ms message: 'network-check-target-ip-10-0-134-2: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:01:35Z" - latency: 2.39429ms message: 'network-check-target-ip-10-0-134-2: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:00:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T07:41:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-15-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-15.ec2.internal uid: 2670696d-4425-4c0b-8a8d-928add626e8f resourceVersion: "46190" uid: c71ef903-d7c5-4b01-afac-6d5ec39cc1ce spec: sourcePod: network-check-source-7f44b6dd87-lszj6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T07:47:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 783.367µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:11:35Z" - latency: 2.169553ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T08:11:35Z" - latency: 900.832µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:10:35Z" - latency: 1.704738ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T08:10:35Z" - latency: 854.952µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:09:35Z" - latency: 1.719ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T08:09:35Z" - latency: 722.127µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:08:35Z" - latency: 1.846449ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T08:08:35Z" - latency: 821.518µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T08:07:35Z" - latency: 1.67314ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T08:07:35Z" kind: List metadata: resourceVersion: ""