apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:13:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-171-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-171.ec2.internal uid: 360b532a-065d-4116-8880-93754cc3ba53 resourceVersion: "33777" uid: 63a663c1-4a80-480b-b550-7b9c36dba7ce spec: sourcePod: network-check-source-56499946bc-xhl25 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T18:20:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 722.77µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:55:38Z" - latency: 704.059µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:54:38Z" - latency: 832.602µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:53:38Z" - latency: 864.976µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:52:38Z" - latency: 754.087µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:51:38Z" - latency: 915.01µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:50:38Z" - latency: 1.062778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:49:38Z" - latency: 1.068909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:48:38Z" - latency: 873.02µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:47:38Z" - latency: 757.671µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:46:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:13:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-171-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-171.ec2.internal uid: 360b532a-065d-4116-8880-93754cc3ba53 resourceVersion: "33778" uid: e066e1d6-a597-4fcf-921d-53a05bf5f721 spec: sourcePod: network-check-source-56499946bc-xhl25 targetEndpoint: a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T18:19:38Z" message: 'load-balancer-api-external: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.582397ms message: 'load-balancer-api-external: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:55:38Z" - latency: 6.760163ms message: 'load-balancer-api-external: resolved host name a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:55:38Z" - latency: 5.667967ms message: 'load-balancer-api-external: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:54:38Z" - latency: 7.972053ms message: 'load-balancer-api-external: resolved host name a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:54:38Z" - latency: 4.228568ms message: 'load-balancer-api-external: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:53:38Z" - latency: 6.599779ms message: 'load-balancer-api-external: resolved host name a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:53:38Z" - latency: 4.562234ms message: 'load-balancer-api-external: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:52:38Z" - latency: 7.176195ms message: 'load-balancer-api-external: resolved host name a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:52:38Z" - latency: 5.681708ms message: 'load-balancer-api-external: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:51:38Z" - latency: 6.522958ms message: 'load-balancer-api-external: resolved host name a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:51:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:13:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-171-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-171.ec2.internal uid: 360b532a-065d-4116-8880-93754cc3ba53 resourceVersion: "33779" uid: e5494e60-96f3-4aad-b7e9-2021f7953b23 spec: sourcePod: network-check-source-56499946bc-xhl25 targetEndpoint: a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T18:19:38Z" message: 'load-balancer-api-internal: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.787878ms message: 'load-balancer-api-internal: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:55:38Z" - latency: 6.730579ms message: 'load-balancer-api-internal: resolved host name a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:55:38Z" - latency: 6.799793ms message: 'load-balancer-api-internal: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:54:38Z" - latency: 7.893154ms message: 'load-balancer-api-internal: resolved host name a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:54:38Z" - latency: 4.417066ms message: 'load-balancer-api-internal: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:53:38Z" - latency: 6.57085ms message: 'load-balancer-api-internal: resolved host name a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:53:38Z" - latency: 4.52795ms message: 'load-balancer-api-internal: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:52:38Z" - latency: 7.136342ms message: 'load-balancer-api-internal: resolved host name a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:52:38Z" - latency: 5.692281ms message: 'load-balancer-api-internal: tcp connection to a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:51:38Z" - latency: 6.513905ms message: 'load-balancer-api-internal: resolved host name a8ed72dbcbfff4f5a924d819d59093ac-3ad467dfd9d4b93a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:51:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:13:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-171-to-network-check-target-ip-10-0-132-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-171.ec2.internal uid: 360b532a-065d-4116-8880-93754cc3ba53 resourceVersion: "33775" uid: 9c172c38-2996-435b-bb56-dc47f22c747c spec: sourcePod: network-check-source-56499946bc-xhl25 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T18:20:38Z" message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.320895ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:55:38Z" - latency: 2.348593ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:54:38Z" - latency: 2.128755ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:53:38Z" - latency: 2.242937ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:52:38Z" - latency: 2.047028ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:51:38Z" - latency: 2.208975ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:50:38Z" - latency: 2.011864ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:49:38Z" - latency: 2.481436ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:48:38Z" - latency: 2.137158ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:47:38Z" - latency: 2.538463ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:46:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:13:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-171-to-network-check-target-ip-10-0-136-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-171.ec2.internal uid: 360b532a-065d-4116-8880-93754cc3ba53 resourceVersion: "33776" uid: dbb4324f-30d5-447a-acf7-43d7f8828717 spec: sourcePod: network-check-source-56499946bc-xhl25 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T18:20:38Z" message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.205956ms message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:55:38Z" - latency: 2.089945ms message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:54:38Z" - latency: 1.760403ms message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:53:38Z" - latency: 1.849939ms message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:52:38Z" - latency: 2.116744ms message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:51:38Z" - latency: 2.351992ms message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:50:38Z" - latency: 2.257243ms message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:49:38Z" - latency: 2.152189ms message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:48:38Z" - latency: 2.119094ms message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:47:38Z" - latency: 2.084214ms message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:46:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:13:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-171-to-network-check-target-ip-10-0-136-171 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-171.ec2.internal uid: 360b532a-065d-4116-8880-93754cc3ba53 resourceVersion: "33773" uid: e1ddeff8-c5ec-4f91-b417-970dd3566f81 spec: sourcePod: network-check-source-56499946bc-xhl25 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T18:20:38Z" message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.159791ms message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:55:38Z" - latency: 1.062644ms message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:54:38Z" - latency: 781.705µs message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:53:38Z" - latency: 1.176972ms message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:52:38Z" - latency: 1.148856ms message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:51:38Z" - latency: 1.077976ms message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:50:38Z" - latency: 807.838µs message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:49:38Z" - latency: 1.251612ms message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:48:38Z" - latency: 883.482µs message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:47:38Z" - latency: 789.773µs message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:46:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:13:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-171-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-171.ec2.internal uid: 360b532a-065d-4116-8880-93754cc3ba53 resourceVersion: "33774" uid: bf12b595-0c03-4d68-bf0c-c368b9b86f65 spec: sourcePod: network-check-source-56499946bc-xhl25 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T18:19:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 780.474µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:55:38Z" - latency: 1.687815ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:55:38Z" - latency: 1.133707ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:54:38Z" - latency: 1.544685ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:54:38Z" - latency: 775.35µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:53:38Z" - latency: 1.522615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:53:38Z" - latency: 1.437857ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:52:38Z" - latency: 1.821045ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:52:38Z" - latency: 874.031µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:51:38Z" - latency: 1.760537ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:51:38Z" kind: List metadata: resourceVersion: ""