apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:44:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-152-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-152.ec2.internal uid: 06958f23-b665-47c0-a285-87f3d7b2cebb resourceVersion: "43587" uid: 5e37c237-0475-4798-8a54-67524aeb6be4 spec: sourcePod: network-check-source-7f44b6dd87-c84m7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T14:51:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 845.72µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:12:16Z" - latency: 1.105804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:11:16Z" - latency: 997.472µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:10:16Z" - latency: 852.538µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:09:16Z" - latency: 1.126954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:08:16Z" - latency: 1.167854ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:07:16Z" - latency: 1.232439ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:06:16Z" - latency: 1.273535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:05:16Z" - latency: 1.273568ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:04:16Z" - latency: 1.160167ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:03:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:44:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-152-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-152.ec2.internal uid: 06958f23-b665-47c0-a285-87f3d7b2cebb resourceVersion: "45905" uid: 0327c5cc-8695-4d93-bd8d-6e0862076388 spec: sourcePod: network-check-source-7f44b6dd87-c84m7 targetEndpoint: a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T14:50:16Z" message: 'load-balancer-api-external: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.512898ms message: 'load-balancer-api-external: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:14:16Z" - latency: 6.677558ms message: 'load-balancer-api-external: resolved host name a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:14:16Z" - latency: 4.324746ms message: 'load-balancer-api-external: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:13:16Z" - latency: 7.436134ms message: 'load-balancer-api-external: resolved host name a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:13:16Z" - latency: 4.492738ms message: 'load-balancer-api-external: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:12:16Z" - latency: 6.564572ms message: 'load-balancer-api-external: resolved host name a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:12:16Z" - latency: 3.693356ms message: 'load-balancer-api-external: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:11:16Z" - latency: 7.130091ms message: 'load-balancer-api-external: resolved host name a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:11:16Z" - latency: 3.894296ms message: 'load-balancer-api-external: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:10:16Z" - latency: 7.687753ms message: 'load-balancer-api-external: resolved host name a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:10:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:44:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-152-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-152.ec2.internal uid: 06958f23-b665-47c0-a285-87f3d7b2cebb resourceVersion: "45906" uid: 0729642e-fbcf-4282-9cf0-e3dad4fb1569 spec: sourcePod: network-check-source-7f44b6dd87-c84m7 targetEndpoint: a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T14:50:16Z" message: 'load-balancer-api-internal: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.545742ms message: 'load-balancer-api-internal: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:14:16Z" - latency: 6.725378ms message: 'load-balancer-api-internal: resolved host name a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:14:16Z" - latency: 4.362076ms message: 'load-balancer-api-internal: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:13:16Z" - latency: 7.337044ms message: 'load-balancer-api-internal: resolved host name a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:13:16Z" - latency: 4.496568ms message: 'load-balancer-api-internal: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:12:16Z" - latency: 6.616227ms message: 'load-balancer-api-internal: resolved host name a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:12:16Z" - latency: 3.762245ms message: 'load-balancer-api-internal: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:11:16Z" - latency: 7.02024ms message: 'load-balancer-api-internal: resolved host name a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:11:16Z" - latency: 4.093741ms message: 'load-balancer-api-internal: tcp connection to a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:10:16Z" - latency: 7.644704ms message: 'load-balancer-api-internal: resolved host name a8e718dbda55d47049b470439d81452c-79692bb074ced0f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:10:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-152-to-network-check-target-ip-10-0-131-210 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-152.ec2.internal uid: 06958f23-b665-47c0-a285-87f3d7b2cebb resourceVersion: "43581" uid: b277c5a3-c61f-456f-bc5d-12ae27ffc93f spec: sourcePod: network-check-source-7f44b6dd87-c84m7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T14:51:16Z" message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.914213ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:12:16Z" - latency: 2.005033ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:11:16Z" - latency: 2.257156ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:10:16Z" - latency: 2.003259ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:09:16Z" - latency: 2.194383ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:08:16Z" - latency: 1.689736ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:07:16Z" - latency: 2.033667ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:06:16Z" - latency: 2.094823ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:05:16Z" - latency: 2.091626ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:04:16Z" - latency: 1.837171ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:03:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-152-to-network-check-target-ip-10-0-133-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-152.ec2.internal uid: 06958f23-b665-47c0-a285-87f3d7b2cebb resourceVersion: "43580" uid: 1e08cae6-fea2-4986-bacf-db7e9f07e3c0 spec: sourcePod: network-check-source-7f44b6dd87-c84m7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T14:51:16Z" message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 871.462µs message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:12:16Z" - latency: 795.276µs message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:11:16Z" - latency: 868.813µs message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:10:16Z" - latency: 839.817µs message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:09:16Z" - latency: 1.122381ms message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:08:16Z" - latency: 892.317µs message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:07:16Z" - latency: 1.113814ms message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:06:16Z" - latency: 874.744µs message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:05:16Z" - latency: 1.052026ms message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:04:16Z" - latency: 900.607µs message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:03:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-152-to-network-check-target-ip-10-0-138-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-152.ec2.internal uid: 06958f23-b665-47c0-a285-87f3d7b2cebb resourceVersion: "43582" uid: 891dacc8-9d51-47a3-b32a-99d353e3a2b0 spec: sourcePod: network-check-source-7f44b6dd87-c84m7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-21T14:51:16Z" message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.037375ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:12:16Z" - latency: 2.140354ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:11:16Z" - latency: 1.786174ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:10:16Z" - latency: 1.867702ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:09:16Z" - latency: 2.121635ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:08:16Z" - latency: 1.870698ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:07:16Z" - latency: 1.719034ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:06:16Z" - latency: 2.216874ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:05:16Z" - latency: 2.34355ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:04:16Z" - latency: 2.26727ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:03:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-152-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-152.ec2.internal uid: 06958f23-b665-47c0-a285-87f3d7b2cebb resourceVersion: "45904" uid: dc0de2e9-7a07-419a-8fe6-6dc14adbab8e spec: sourcePod: network-check-source-7f44b6dd87-c84m7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T14:50:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 867.98µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:14:16Z" - latency: 1.907755ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:14:16Z" - latency: 722.052µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:13:16Z" - latency: 2.428726ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:13:16Z" - latency: 1.088919ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:12:16Z" - latency: 1.82565ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:12:16Z" - latency: 797.504µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:11:16Z" - latency: 1.959026ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:11:16Z" - latency: 748.28µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:10:16Z" - latency: 2.291066ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:10:16Z" kind: List metadata: resourceVersion: ""