apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:20:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-143-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-143.ec2.internal uid: e8c60722-f144-4650-9431-df43e290ebf4 resourceVersion: "78864" uid: f1fd5299-3cf1-4261-b464-3d8f506eecc8 spec: sourcePod: network-check-source-65bdbbff45-r2p2q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-31T14:27:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.181896ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:16:04Z" - latency: 953.199µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:15:04Z" - latency: 1.424202ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:14:04Z" - latency: 924.283µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:13:04Z" - latency: 907.565µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:12:04Z" - latency: 882.18µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:11:04Z" - latency: 704.224µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:10:04Z" - latency: 807.8µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:09:04Z" - latency: 1.484373ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:08:04Z" - latency: 1.311333ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:07:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:20:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-143-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-143.ec2.internal uid: e8c60722-f144-4650-9431-df43e290ebf4 resourceVersion: "76579" uid: 638cbe51-c240-4807-9552-7dec91705d6d spec: sourcePod: network-check-source-65bdbbff45-r2p2q targetEndpoint: ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T14:26:04Z" message: 'load-balancer-api-external: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.229598ms message: 'load-balancer-api-external: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:14:04Z" - latency: 8.220834ms message: 'load-balancer-api-external: resolved host name ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:14:04Z" - latency: 4.364717ms message: 'load-balancer-api-external: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:13:04Z" - latency: 9.449727ms message: 'load-balancer-api-external: resolved host name ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:13:04Z" - latency: 3.911173ms message: 'load-balancer-api-external: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:12:04Z" - latency: 7.021522ms message: 'load-balancer-api-external: resolved host name ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:12:04Z" - latency: 4.344637ms message: 'load-balancer-api-external: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:11:04Z" - latency: 6.615791ms message: 'load-balancer-api-external: resolved host name ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:11:04Z" - latency: 5.718409ms message: 'load-balancer-api-external: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:10:04Z" - latency: 7.580302ms message: 'load-balancer-api-external: resolved host name ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:10:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:20:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-143-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-143.ec2.internal uid: e8c60722-f144-4650-9431-df43e290ebf4 resourceVersion: "76580" uid: 4e5b2e78-a2e4-4999-a89e-36ae04568433 spec: sourcePod: network-check-source-65bdbbff45-r2p2q targetEndpoint: ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T14:26:04Z" message: 'load-balancer-api-internal: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.301964ms message: 'load-balancer-api-internal: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:14:04Z" - latency: 8.172088ms message: 'load-balancer-api-internal: resolved host name ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:14:04Z" - latency: 4.272617ms message: 'load-balancer-api-internal: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:13:04Z" - latency: 9.521542ms message: 'load-balancer-api-internal: resolved host name ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:13:04Z" - latency: 3.017538ms message: 'load-balancer-api-internal: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:12:04Z" - latency: 7.055761ms message: 'load-balancer-api-internal: resolved host name ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:12:04Z" - latency: 4.211015ms message: 'load-balancer-api-internal: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:11:04Z" - latency: 6.595355ms message: 'load-balancer-api-internal: resolved host name ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:11:04Z" - latency: 6.382956ms message: 'load-balancer-api-internal: tcp connection to ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:10:04Z" - latency: 7.481384ms message: 'load-balancer-api-internal: resolved host name ac4fcb92e9e884355842fc63968fed57-62dd95b695759b25.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:10:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:20:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-143-to-network-check-target-ip-10-0-130-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-143.ec2.internal uid: e8c60722-f144-4650-9431-df43e290ebf4 resourceVersion: "78863" uid: ba9579a7-7114-4a26-b1e2-52def306c995 spec: sourcePod: network-check-source-65bdbbff45-r2p2q targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-31T14:27:04Z" message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.44085ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:16:04Z" - latency: 2.311612ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:15:04Z" - latency: 2.433886ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:14:04Z" - latency: 2.190358ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:13:04Z" - latency: 2.34522ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:12:04Z" - latency: 2.284709ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:11:04Z" - latency: 2.327911ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:10:04Z" - latency: 2.219733ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:09:04Z" - latency: 2.511289ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:08:04Z" - latency: 2.237462ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:07:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:20:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-143-to-network-check-target-ip-10-0-132-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-143.ec2.internal uid: e8c60722-f144-4650-9431-df43e290ebf4 resourceVersion: "78862" uid: e6aba246-b3e9-4d40-b279-636c085885f4 spec: sourcePod: network-check-source-65bdbbff45-r2p2q targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-31T14:27:04Z" message: 'network-check-target-ip-10-0-132-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.928393ms message: 'network-check-target-ip-10-0-132-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:16:04Z" - latency: 2.154142ms message: 'network-check-target-ip-10-0-132-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:15:04Z" - latency: 2.024044ms message: 'network-check-target-ip-10-0-132-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:14:04Z" - latency: 1.782113ms message: 'network-check-target-ip-10-0-132-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:13:04Z" - latency: 1.804189ms message: 'network-check-target-ip-10-0-132-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:12:04Z" - latency: 1.657171ms message: 'network-check-target-ip-10-0-132-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:11:04Z" - latency: 2.226494ms message: 'network-check-target-ip-10-0-132-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:10:04Z" - latency: 2.104374ms message: 'network-check-target-ip-10-0-132-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:09:04Z" - latency: 2.073786ms message: 'network-check-target-ip-10-0-132-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:08:04Z" - latency: 1.838716ms message: 'network-check-target-ip-10-0-132-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:07:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:20:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-143-to-network-check-target-ip-10-0-139-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-143.ec2.internal uid: e8c60722-f144-4650-9431-df43e290ebf4 resourceVersion: "78861" uid: 622361c2-0122-4469-a5d0-d7d585a15f83 spec: sourcePod: network-check-source-65bdbbff45-r2p2q targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-31T14:27:04Z" message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 982.958µs message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:16:04Z" - latency: 1.370165ms message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:15:04Z" - latency: 1.104051ms message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:14:04Z" - latency: 887.396µs message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:13:04Z" - latency: 802.574µs message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:12:04Z" - latency: 1.474776ms message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:11:04Z" - latency: 1.279692ms message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:10:04Z" - latency: 1.161619ms message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:09:04Z" - latency: 1.365239ms message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:08:04Z" - latency: 816.765µs message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:07:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:20:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-143-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-143.ec2.internal uid: e8c60722-f144-4650-9431-df43e290ebf4 resourceVersion: "76577" uid: 99ee34c9-1207-4810-ab35-fcf271d87f5c spec: sourcePod: network-check-source-65bdbbff45-r2p2q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-31T14:26:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 876.253µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:14:04Z" - latency: 1.691923ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T15:14:04Z" - latency: 1.000137ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:13:04Z" - latency: 1.736751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T15:13:04Z" - latency: 863.796µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:12:04Z" - latency: 1.673413ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T15:12:04Z" - latency: 877.527µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:11:04Z" - latency: 1.8042ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T15:11:04Z" - latency: 1.223335ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:10:04Z" - latency: 1.633174ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T15:10:04Z" kind: List metadata: resourceVersion: ""