apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:47:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-243-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-243.ec2.internal uid: e06a6319-4867-40e0-99fc-23469c2f2ef8 resourceVersion: "50508" uid: cc4ddc9c-bc48-43c5-9ca4-ea8b9f4912b7 spec: sourcePod: network-check-source-6947749cfc-fdzh7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T21:55:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.536317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:23:01Z" - latency: 1.399483ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:22:01Z" - latency: 1.020754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:21:01Z" - latency: 981.247µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:20:01Z" - latency: 1.169133ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:19:01Z" - latency: 955.63µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:18:01Z" - latency: 943.387µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:17:01Z" - latency: 970.729µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:16:01Z" - latency: 1.136778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:15:01Z" - latency: 1.328961ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:14:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:47:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-243-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-243.ec2.internal uid: e06a6319-4867-40e0-99fc-23469c2f2ef8 resourceVersion: "51614" uid: 81e08687-1727-47c1-b4ff-c6a98c54e386 spec: sourcePod: network-check-source-6947749cfc-fdzh7 targetEndpoint: a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T21:54:01Z" message: 'load-balancer-api-external: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.177775ms message: 'load-balancer-api-external: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:24:01Z" - latency: 7.640498ms message: 'load-balancer-api-external: resolved host name a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:24:01Z" - latency: 5.484398ms message: 'load-balancer-api-external: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:23:01Z" - latency: 12.133324ms message: 'load-balancer-api-external: resolved host name a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:23:01Z" - latency: 4.587022ms message: 'load-balancer-api-external: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:22:01Z" - latency: 12.517013ms message: 'load-balancer-api-external: resolved host name a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:22:01Z" - latency: 4.519621ms message: 'load-balancer-api-external: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:21:01Z" - latency: 9.442157ms message: 'load-balancer-api-external: resolved host name a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:21:01Z" - latency: 3.914334ms message: 'load-balancer-api-external: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:20:01Z" - latency: 8.444709ms message: 'load-balancer-api-external: resolved host name a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:20:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:47:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-243-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-243.ec2.internal uid: e06a6319-4867-40e0-99fc-23469c2f2ef8 resourceVersion: "51615" uid: bea55b36-9f48-4148-8263-f6654f1ead3f spec: sourcePod: network-check-source-6947749cfc-fdzh7 targetEndpoint: a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T21:54:01Z" message: 'load-balancer-api-internal: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.963493ms message: 'load-balancer-api-internal: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:24:01Z" - latency: 7.695904ms message: 'load-balancer-api-internal: resolved host name a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:24:01Z" - latency: 5.495068ms message: 'load-balancer-api-internal: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:23:01Z" - latency: 12.085485ms message: 'load-balancer-api-internal: resolved host name a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:23:01Z" - latency: 4.246218ms message: 'load-balancer-api-internal: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:22:01Z" - latency: 12.601239ms message: 'load-balancer-api-internal: resolved host name a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:22:01Z" - latency: 4.522653ms message: 'load-balancer-api-internal: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:21:01Z" - latency: 9.401649ms message: 'load-balancer-api-internal: resolved host name a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:21:01Z" - latency: 3.910496ms message: 'load-balancer-api-internal: tcp connection to a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:20:01Z" - latency: 8.549057ms message: 'load-balancer-api-internal: resolved host name a3e655818acb34721887d3b096f5d5a8-30cbad351bc8df20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:20:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:47:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-243-to-network-check-target-ip-10-0-129-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-243.ec2.internal uid: e06a6319-4867-40e0-99fc-23469c2f2ef8 resourceVersion: "50507" uid: 4ceb17af-84e9-4696-b23b-dd4d3ea23e04 spec: sourcePod: network-check-source-6947749cfc-fdzh7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T21:55:01Z" message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.999685ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:23:01Z" - latency: 2.881193ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:22:01Z" - latency: 2.189009ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:21:01Z" - latency: 2.348667ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:20:01Z" - latency: 2.196009ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:19:01Z" - latency: 2.159664ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:18:01Z" - latency: 1.94642ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:17:01Z" - latency: 2.061888ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:16:01Z" - latency: 1.803288ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:15:01Z" - latency: 2.285752ms message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:14:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:47:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-243-to-network-check-target-ip-10-0-130-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-243.ec2.internal uid: e06a6319-4867-40e0-99fc-23469c2f2ef8 resourceVersion: "50506" uid: cf00af22-c10b-4bff-a64c-440d43a59b0e spec: sourcePod: network-check-source-6947749cfc-fdzh7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T21:55:01Z" message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.89257ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:23:01Z" - latency: 2.462033ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:22:01Z" - latency: 1.975918ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:21:01Z" - latency: 1.963498ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:20:01Z" - latency: 1.984238ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:19:01Z" - latency: 2.01091ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:18:01Z" - latency: 1.732642ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:17:01Z" - latency: 1.931781ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:16:01Z" - latency: 1.836999ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:15:01Z" - latency: 2.310542ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:14:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:47:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-243-to-network-check-target-ip-10-0-133-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-243.ec2.internal uid: e06a6319-4867-40e0-99fc-23469c2f2ef8 resourceVersion: "50505" uid: 038810ea-74fc-411c-9242-c04b034f8931 spec: sourcePod: network-check-source-6947749cfc-fdzh7 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T21:55:01Z" message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 937.741µs message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:23:01Z" - latency: 1.318462ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:22:01Z" - latency: 894.745µs message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:21:01Z" - latency: 1.156418ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:20:01Z" - latency: 1.131918ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:19:01Z" - latency: 1.437448ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:18:01Z" - latency: 925.534µs message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:17:01Z" - latency: 1.035806ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:16:01Z" - latency: 817.72µs message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:15:01Z" - latency: 1.350695ms message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:14:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:47:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-243-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-243.ec2.internal uid: e06a6319-4867-40e0-99fc-23469c2f2ef8 resourceVersion: "51613" uid: 9676f148-ce85-4ca0-ad0c-a162f72c9290 spec: sourcePod: network-check-source-6947749cfc-fdzh7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T21:54:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.173825ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:24:01Z" - latency: 1.709136ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:24:01Z" - latency: 972.804µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:23:01Z" - latency: 1.479143ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:23:01Z" - latency: 1.140659ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:22:01Z" - latency: 2.057757ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:22:01Z" - latency: 965.207µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:21:01Z" - latency: 1.903277ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:21:01Z" - latency: 928.675µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:20:01Z" - latency: 1.617424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:20:01Z" kind: List metadata: resourceVersion: ""