apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T12:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-175-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-175.ec2.internal uid: aa9ea4d5-4d6e-4411-8ccb-28396dd43c38 resourceVersion: "29667" uid: 752fb83c-7112-4001-8423-d1132f84466f spec: sourcePod: network-check-source-dbd9cf844-xsbq4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T13:05:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 943.02µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:12:55Z" - latency: 876.576µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:11:55Z" - latency: 1.129989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:10:55Z" - latency: 950.366µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:09:55Z" - latency: 984.818µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:08:55Z" - latency: 938.94µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:07:55Z" - latency: 1.127932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:06:55Z" - latency: 955.088µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:05:55Z" - latency: 990.1µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:04:55Z" - latency: 843.904µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:03:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T12:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-175-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-175.ec2.internal uid: aa9ea4d5-4d6e-4411-8ccb-28396dd43c38 resourceVersion: "32242" uid: 88185338-0c12-49ff-bf51-e5804ef8fe7d spec: sourcePod: network-check-source-dbd9cf844-xsbq4 targetEndpoint: ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T13:04:55Z" message: 'load-balancer-api-external: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.566695ms message: 'load-balancer-api-external: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:16:55Z" - latency: 7.866017ms message: 'load-balancer-api-external: resolved host name ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:16:55Z" - latency: 4.403338ms message: 'load-balancer-api-external: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:15:55Z" - latency: 8.522568ms message: 'load-balancer-api-external: resolved host name ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:15:55Z" - latency: 4.665431ms message: 'load-balancer-api-external: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:14:55Z" - latency: 8.546878ms message: 'load-balancer-api-external: resolved host name ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:14:55Z" - latency: 4.495038ms message: 'load-balancer-api-external: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:13:55Z" - latency: 9.684509ms message: 'load-balancer-api-external: resolved host name ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:13:55Z" - latency: 5.246438ms message: 'load-balancer-api-external: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:12:55Z" - latency: 8.353746ms message: 'load-balancer-api-external: resolved host name ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:12:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T12:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-175-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-175.ec2.internal uid: aa9ea4d5-4d6e-4411-8ccb-28396dd43c38 resourceVersion: "32243" uid: fe41eb75-38ad-4bc5-833d-a8b382440de5 spec: sourcePod: network-check-source-dbd9cf844-xsbq4 targetEndpoint: ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T13:04:55Z" message: 'load-balancer-api-internal: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.565145ms message: 'load-balancer-api-internal: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:16:55Z" - latency: 7.88316ms message: 'load-balancer-api-internal: resolved host name ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:16:55Z" - latency: 4.409385ms message: 'load-balancer-api-internal: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:15:55Z" - latency: 8.539698ms message: 'load-balancer-api-internal: resolved host name ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:15:55Z" - latency: 4.282389ms message: 'load-balancer-api-internal: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:14:55Z" - latency: 8.596253ms message: 'load-balancer-api-internal: resolved host name ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:14:55Z" - latency: 4.478965ms message: 'load-balancer-api-internal: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:13:55Z" - latency: 9.721501ms message: 'load-balancer-api-internal: resolved host name ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:13:55Z" - latency: 5.209316ms message: 'load-balancer-api-internal: tcp connection to ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:12:55Z" - latency: 8.395102ms message: 'load-balancer-api-internal: resolved host name ae607d947684345728abe2873ed1fe51-5ac6642f1fb52d0d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:12:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T12:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-175-to-network-check-target-ip-10-0-135-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-175.ec2.internal uid: aa9ea4d5-4d6e-4411-8ccb-28396dd43c38 resourceVersion: "29666" uid: 2a762760-bc00-4dd9-ac60-d69265a038b1 spec: sourcePod: network-check-source-dbd9cf844-xsbq4 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T13:05:55Z" message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.365573ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:12:55Z" - latency: 2.339283ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:11:55Z" - latency: 2.55524ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:10:55Z" - latency: 2.439803ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:09:55Z" - latency: 2.66212ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:08:55Z" - latency: 2.391721ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:07:55Z" - latency: 2.291399ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:06:55Z" - latency: 2.997844ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:05:55Z" - latency: 2.354395ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:04:55Z" - latency: 2.365241ms message: 'network-check-target-ip-10-0-135-157: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:03:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T12:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-175-to-network-check-target-ip-10-0-137-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-175.ec2.internal uid: aa9ea4d5-4d6e-4411-8ccb-28396dd43c38 resourceVersion: "29665" uid: d686e450-5523-4f2b-99f7-d34121096015 spec: sourcePod: network-check-source-dbd9cf844-xsbq4 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T13:05:55Z" message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.23628ms message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:12:55Z" - latency: 2.322396ms message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:11:55Z" - latency: 2.208171ms message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:10:55Z" - latency: 2.572686ms message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:09:55Z" - latency: 2.392234ms message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:08:55Z" - latency: 2.281932ms message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:07:55Z" - latency: 2.764405ms message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:06:55Z" - latency: 2.444163ms message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:05:55Z" - latency: 2.29398ms message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:04:55Z" - latency: 2.390659ms message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:03:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T12:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-175-to-network-check-target-ip-10-0-142-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-175.ec2.internal uid: aa9ea4d5-4d6e-4411-8ccb-28396dd43c38 resourceVersion: "29664" uid: d18b7cd0-a414-46a4-8ee5-b428f858e410 spec: sourcePod: network-check-source-dbd9cf844-xsbq4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T13:05:55Z" message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 826.872µs message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:12:55Z" - latency: 854.926µs message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:11:55Z" - latency: 762.975µs message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:10:55Z" - latency: 967.998µs message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:09:55Z" - latency: 882µs message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:08:55Z" - latency: 929.29µs message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:07:55Z" - latency: 1.494833ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:06:55Z" - latency: 807.701µs message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:05:55Z" - latency: 1.057364ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:04:55Z" - latency: 761.764µs message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:03:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T12:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-175-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-175.ec2.internal uid: aa9ea4d5-4d6e-4411-8ccb-28396dd43c38 resourceVersion: "32241" uid: 05ac7a5e-b3ee-49d7-ab86-588ce0110816 spec: sourcePod: network-check-source-dbd9cf844-xsbq4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T13:04:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.071617ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:16:55Z" - latency: 1.717783ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T13:16:55Z" - latency: 784.479µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:15:55Z" - latency: 1.663488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T13:15:55Z" - latency: 874.502µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:14:55Z" - latency: 1.773382ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T13:14:55Z" - latency: 717.767µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:13:55Z" - latency: 1.781862ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T13:13:55Z" - latency: 882.686µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:12:55Z" - latency: 2.31082ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T13:12:55Z" kind: List metadata: resourceVersion: ""