apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-32-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-32.ec2.internal uid: 39cf4aad-339e-476a-a480-26329ddbea5b resourceVersion: "44030" uid: 54f97e65-3689-4abf-8468-c2530d1ee046 spec: sourcePod: network-check-source-8894fc9bd-t9c6n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T18:56:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.221129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:54Z" - latency: 867.141µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:16:54Z" - latency: 1.016954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:15:54Z" - latency: 721.255µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:14:54Z" - latency: 1.007646ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:13:54Z" - latency: 697.497µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:54Z" - latency: 909.571µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:11:54Z" - latency: 918.704µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:10:54Z" - latency: 962.01µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:54Z" - latency: 896.786µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-32-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-32.ec2.internal uid: 39cf4aad-339e-476a-a480-26329ddbea5b resourceVersion: "46033" uid: 4ffd44d9-612d-4338-9551-584ab76e12f3 spec: sourcePod: network-check-source-8894fc9bd-t9c6n targetEndpoint: a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:55:54Z" message: 'load-balancer-api-external: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.442314ms message: 'load-balancer-api-external: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:19:54Z" - latency: 7.190451ms message: 'load-balancer-api-external: resolved host name a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:19:54Z" - latency: 4.237151ms message: 'load-balancer-api-external: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:18:54Z" - latency: 9.730128ms message: 'load-balancer-api-external: resolved host name a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:18:54Z" - latency: 4.942077ms message: 'load-balancer-api-external: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:54Z" - latency: 11.559293ms message: 'load-balancer-api-external: resolved host name a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:17:54Z" - latency: 4.977857ms message: 'load-balancer-api-external: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:16:54Z" - latency: 12.325389ms message: 'load-balancer-api-external: resolved host name a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:16:54Z" - latency: 4.922682ms message: 'load-balancer-api-external: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:15:54Z" - latency: 7.063651ms message: 'load-balancer-api-external: resolved host name a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:15:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-32-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-32.ec2.internal uid: 39cf4aad-339e-476a-a480-26329ddbea5b resourceVersion: "46032" uid: 10e00430-4a49-48c2-8315-50836be9f3a3 spec: sourcePod: network-check-source-8894fc9bd-t9c6n targetEndpoint: a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:55:54Z" message: 'load-balancer-api-internal: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.508451ms message: 'load-balancer-api-internal: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:19:54Z" - latency: 7.132135ms message: 'load-balancer-api-internal: resolved host name a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:19:54Z" - latency: 4.973303ms message: 'load-balancer-api-internal: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:18:54Z" - latency: 9.699283ms message: 'load-balancer-api-internal: resolved host name a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:18:54Z" - latency: 4.799438ms message: 'load-balancer-api-internal: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:54Z" - latency: 11.648755ms message: 'load-balancer-api-internal: resolved host name a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:17:54Z" - latency: 5.176748ms message: 'load-balancer-api-internal: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:16:54Z" - latency: 12.25753ms message: 'load-balancer-api-internal: resolved host name a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:16:54Z" - latency: 4.86534ms message: 'load-balancer-api-internal: tcp connection to a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:15:54Z" - latency: 7.028404ms message: 'load-balancer-api-internal: resolved host name a1cc2ebcc515f40f4a156f54a944ff57-6f5bf677d12cd03c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:15:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-32-to-network-check-target-ip-10-0-129-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-32.ec2.internal uid: 39cf4aad-339e-476a-a480-26329ddbea5b resourceVersion: "44029" uid: 58f5acd6-c819-446c-b812-a5fd986247c2 spec: sourcePod: network-check-source-8894fc9bd-t9c6n targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:56:54Z" message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.072231ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:54Z" - latency: 2.269847ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:16:54Z" - latency: 2.130326ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:15:54Z" - latency: 1.691429ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:14:54Z" - latency: 2.04614ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:13:54Z" - latency: 2.413278ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:54Z" - latency: 2.431806ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:11:54Z" - latency: 2.341275ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:10:54Z" - latency: 2.201919ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:54Z" - latency: 2.278164ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-32-to-network-check-target-ip-10-0-130-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-32.ec2.internal uid: 39cf4aad-339e-476a-a480-26329ddbea5b resourceVersion: "44027" uid: 53cf367f-b6a9-466d-89ec-5fe453433353 spec: sourcePod: network-check-source-8894fc9bd-t9c6n targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:56:54Z" message: 'network-check-target-ip-10-0-130-32: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.282576ms message: 'network-check-target-ip-10-0-130-32: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:54Z" - latency: 948.514µs message: 'network-check-target-ip-10-0-130-32: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:16:54Z" - latency: 900.53µs message: 'network-check-target-ip-10-0-130-32: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:15:54Z" - latency: 1.048907ms message: 'network-check-target-ip-10-0-130-32: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:14:54Z" - latency: 972.731µs message: 'network-check-target-ip-10-0-130-32: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:13:54Z" - latency: 1.319442ms message: 'network-check-target-ip-10-0-130-32: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:54Z" - latency: 832.735µs message: 'network-check-target-ip-10-0-130-32: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:11:54Z" - latency: 1.208635ms message: 'network-check-target-ip-10-0-130-32: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:10:54Z" - latency: 968.246µs message: 'network-check-target-ip-10-0-130-32: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:54Z" - latency: 712.685µs message: 'network-check-target-ip-10-0-130-32: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-32-to-network-check-target-ip-10-0-137-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-32.ec2.internal uid: 39cf4aad-339e-476a-a480-26329ddbea5b resourceVersion: "44028" uid: 20e111ac-4186-4166-ade8-5379807603df spec: sourcePod: network-check-source-8894fc9bd-t9c6n targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:56:54Z" message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.337986ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:54Z" - latency: 2.33174ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:16:54Z" - latency: 2.177094ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:15:54Z" - latency: 1.915687ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:14:54Z" - latency: 2.398731ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:13:54Z" - latency: 2.478766ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:54Z" - latency: 2.36774ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:11:54Z" - latency: 2.039136ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:10:54Z" - latency: 2.876482ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:54Z" - latency: 2.333649ms message: 'network-check-target-ip-10-0-137-223: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-32-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-32.ec2.internal uid: 39cf4aad-339e-476a-a480-26329ddbea5b resourceVersion: "46031" uid: 3ebca27f-0a3f-4e55-955b-5aafb94aa595 spec: sourcePod: network-check-source-8894fc9bd-t9c6n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T18:55:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 970.318µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:19:54Z" - latency: 1.754104ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:19:54Z" - latency: 1.030851ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:18:54Z" - latency: 1.467626ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:18:54Z" - latency: 1.233168ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:17:54Z" - latency: 1.722279ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:17:54Z" - latency: 730.825µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:16:54Z" - latency: 1.616667ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:16:54Z" - latency: 1.129211ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:15:54Z" - latency: 1.731402ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:15:54Z" kind: List metadata: resourceVersion: ""