apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:16:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-144-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-144.ec2.internal uid: 5d39c9fd-a89e-46f9-9552-f14ddbf81785 resourceVersion: "19405" uid: a1b09224-6bbc-4de4-8401-3968c249e341 spec: sourcePod: network-check-source-7f44b6dd87-rznw6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T08:23:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 838.924µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:37:47Z" - latency: 921.889µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:36:47Z" - latency: 922.784µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:35:47Z" - latency: 1.072818ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:34:47Z" - latency: 1.416415ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:33:47Z" - latency: 970.306µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:32:47Z" - latency: 874.549µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:31:47Z" - latency: 914.427µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:30:47Z" - latency: 1.410949ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:29:47Z" - latency: 877.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:28:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:16:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-144-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-144.ec2.internal uid: 5d39c9fd-a89e-46f9-9552-f14ddbf81785 resourceVersion: "20646" uid: 85a03bce-8b01-48bb-9115-8758afe561c2 spec: sourcePod: network-check-source-7f44b6dd87-rznw6 targetEndpoint: a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T08:22:47Z" message: 'load-balancer-api-external: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.000987ms message: 'load-balancer-api-external: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:40:47Z" - latency: 6.80687ms message: 'load-balancer-api-external: resolved host name a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:40:47Z" - latency: 3.793353ms message: 'load-balancer-api-external: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:39:47Z" - latency: 8.439921ms message: 'load-balancer-api-external: resolved host name a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:39:47Z" - latency: 4.852978ms message: 'load-balancer-api-external: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:38:47Z" - latency: 8.881574ms message: 'load-balancer-api-external: resolved host name a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:38:47Z" - latency: 4.607269ms message: 'load-balancer-api-external: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:37:47Z" - latency: 8.276344ms message: 'load-balancer-api-external: resolved host name a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:37:47Z" - latency: 4.018886ms message: 'load-balancer-api-external: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:36:47Z" - latency: 7.884081ms message: 'load-balancer-api-external: resolved host name a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:36:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:16:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-144-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-144.ec2.internal uid: 5d39c9fd-a89e-46f9-9552-f14ddbf81785 resourceVersion: "20647" uid: a4dc0aa7-53dd-4737-9307-7f0ce94d846b spec: sourcePod: network-check-source-7f44b6dd87-rznw6 targetEndpoint: a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T08:22:47Z" message: 'load-balancer-api-internal: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.347389ms message: 'load-balancer-api-internal: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:40:47Z" - latency: 6.878984ms message: 'load-balancer-api-internal: resolved host name a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:40:47Z" - latency: 3.751039ms message: 'load-balancer-api-internal: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:39:47Z" - latency: 8.471783ms message: 'load-balancer-api-internal: resolved host name a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:39:47Z" - latency: 4.901327ms message: 'load-balancer-api-internal: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:38:47Z" - latency: 8.852013ms message: 'load-balancer-api-internal: resolved host name a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:38:47Z" - latency: 4.65116ms message: 'load-balancer-api-internal: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:37:47Z" - latency: 8.130357ms message: 'load-balancer-api-internal: resolved host name a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:37:47Z" - latency: 5.809146ms message: 'load-balancer-api-internal: tcp connection to a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:36:47Z" - latency: 7.83605ms message: 'load-balancer-api-internal: resolved host name a53d67227abe74b4f97ccf81a5ce2b35-167c72e75fd8dde3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:36:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:16:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-144-to-network-check-target-ip-10-0-133-172 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-144.ec2.internal uid: 5d39c9fd-a89e-46f9-9552-f14ddbf81785 resourceVersion: "19402" uid: 8562fe5f-f3bf-4c5e-8cb8-277eb301619d spec: sourcePod: network-check-source-7f44b6dd87-rznw6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T08:23:47Z" message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.998729ms message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:37:47Z" - latency: 2.890747ms message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:36:47Z" - latency: 2.330347ms message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:35:47Z" - latency: 2.228395ms message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:34:47Z" - latency: 2.332004ms message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:33:47Z" - latency: 2.225852ms message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:32:47Z" - latency: 2.072278ms message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:31:47Z" - latency: 2.088574ms message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:30:47Z" - latency: 2.147796ms message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:29:47Z" - latency: 2.651188ms message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:28:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:16:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-144-to-network-check-target-ip-10-0-135-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-144.ec2.internal uid: 5d39c9fd-a89e-46f9-9552-f14ddbf81785 resourceVersion: "19401" uid: eb12377e-abab-4cd0-aba0-6bfb1f86fd7c spec: sourcePod: network-check-source-7f44b6dd87-rznw6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T08:23:47Z" message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 845.065µs message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:37:47Z" - latency: 1.304366ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:36:47Z" - latency: 1.270281ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:35:47Z" - latency: 813.028µs message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:34:47Z" - latency: 828.852µs message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:33:47Z" - latency: 925.654µs message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:32:47Z" - latency: 798.301µs message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:31:47Z" - latency: 1.72225ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:30:47Z" - latency: 831.432µs message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:29:47Z" - latency: 1.247325ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:28:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:16:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-144-to-network-check-target-ip-10-0-137-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-144.ec2.internal uid: 5d39c9fd-a89e-46f9-9552-f14ddbf81785 resourceVersion: "19404" uid: 289f9c11-05d3-4734-80e9-9e0d65d06d22 spec: sourcePod: network-check-source-7f44b6dd87-rznw6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T08:23:47Z" message: 'network-check-target-ip-10-0-137-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.026918ms message: 'network-check-target-ip-10-0-137-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:37:47Z" - latency: 2.934831ms message: 'network-check-target-ip-10-0-137-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:36:47Z" - latency: 2.345379ms message: 'network-check-target-ip-10-0-137-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:35:47Z" - latency: 2.48864ms message: 'network-check-target-ip-10-0-137-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:34:47Z" - latency: 1.943612ms message: 'network-check-target-ip-10-0-137-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:33:47Z" - latency: 2.370691ms message: 'network-check-target-ip-10-0-137-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:32:47Z" - latency: 1.983285ms message: 'network-check-target-ip-10-0-137-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:31:47Z" - latency: 2.448623ms message: 'network-check-target-ip-10-0-137-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:30:47Z" - latency: 1.980731ms message: 'network-check-target-ip-10-0-137-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:29:47Z" - latency: 1.982634ms message: 'network-check-target-ip-10-0-137-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:28:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:16:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-144-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-144.ec2.internal uid: 5d39c9fd-a89e-46f9-9552-f14ddbf81785 resourceVersion: "20645" uid: feaccc35-03da-41f4-b4d7-df825fa096d7 spec: sourcePod: network-check-source-7f44b6dd87-rznw6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T08:22:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 764.743µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:40:47Z" - latency: 1.945404ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T08:40:47Z" - latency: 846.02µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:39:47Z" - latency: 1.829303ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T08:39:47Z" - latency: 799.806µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:38:47Z" - latency: 1.722403ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T08:38:47Z" - latency: 794.025µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:37:47Z" - latency: 1.845334ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T08:37:47Z" - latency: 1.302045ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:36:47Z" - latency: 1.562545ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T08:36:47Z" kind: List metadata: resourceVersion: ""