apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T09:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-66-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-66.ec2.internal
      uid: 45fc4906-cb7d-4b4c-af18-4a5ab47375d9
    resourceVersion: "14408"
    uid: 60f7c144-950d-49fd-8d66-3d9c38a455bd
  spec:
    sourcePod: network-check-source-6f8b768455-r7shg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T09:09:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.425354ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:09:27Z"
    - latency: 1.04003ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:08:27Z"
    - latency: 1.121245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:07:27Z"
    - latency: 1.051435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:06:27Z"
    - latency: 1.23572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:05:27Z"
    - latency: 930.27µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:04:27Z"
    - latency: 932.3µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:03:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T09:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-66-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-66.ec2.internal
      uid: 45fc4906-cb7d-4b4c-af18-4a5ab47375d9
    resourceVersion: "14077"
    uid: 7b61e12e-3b57-4db9-9faa-77fca01daf3c
  spec:
    sourcePod: network-check-source-6f8b768455-r7shg
    targetEndpoint: abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T09:08:27Z"
      message: 'load-balancer-api-external: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.945699ms
      message: 'load-balancer-api-external: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:08:27Z"
    - latency: 7.805495ms
      message: 'load-balancer-api-external: resolved host name abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:08:27Z"
    - latency: 5.822792ms
      message: 'load-balancer-api-external: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:07:27Z"
    - latency: 6.1144ms
      message: 'load-balancer-api-external: resolved host name abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:07:27Z"
    - latency: 5.411379ms
      message: 'load-balancer-api-external: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:06:27Z"
    - latency: 8.868084ms
      message: 'load-balancer-api-external: resolved host name abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:06:27Z"
    - latency: 4.225171ms
      message: 'load-balancer-api-external: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:05:27Z"
    - latency: 6.739653ms
      message: 'load-balancer-api-external: resolved host name abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:05:27Z"
    - latency: 5.007317ms
      message: 'load-balancer-api-external: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:04:27Z"
    - latency: 10.363806ms
      message: 'load-balancer-api-external: resolved host name abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:04:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T09:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-66-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-66.ec2.internal
      uid: 45fc4906-cb7d-4b4c-af18-4a5ab47375d9
    resourceVersion: "14076"
    uid: 94d0fe62-e3e3-4794-a5a9-8c8ee9d7f5d4
  spec:
    sourcePod: network-check-source-6f8b768455-r7shg
    targetEndpoint: abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T09:08:27Z"
      message: 'load-balancer-api-internal: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.899416ms
      message: 'load-balancer-api-internal: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:08:27Z"
    - latency: 7.758797ms
      message: 'load-balancer-api-internal: resolved host name abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:08:27Z"
    - latency: 5.482659ms
      message: 'load-balancer-api-internal: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:07:27Z"
    - latency: 6.234394ms
      message: 'load-balancer-api-internal: resolved host name abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:07:27Z"
    - latency: 10.618577ms
      message: 'load-balancer-api-internal: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:06:27Z"
    - latency: 8.988037ms
      message: 'load-balancer-api-internal: resolved host name abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:06:27Z"
    - latency: 4.793646ms
      message: 'load-balancer-api-internal: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:05:27Z"
    - latency: 6.817715ms
      message: 'load-balancer-api-internal: resolved host name abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:05:27Z"
    - latency: 5.023087ms
      message: 'load-balancer-api-internal: tcp connection to abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:04:27Z"
    - latency: 10.457755ms
      message: 'load-balancer-api-internal: resolved host name abc9249085f474498807619469945a0f-1cd01c15505a2ba4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:04:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T09:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-66-to-network-check-target-ip-10-0-132-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-66.ec2.internal
      uid: 45fc4906-cb7d-4b4c-af18-4a5ab47375d9
    resourceVersion: "14405"
    uid: cfb34434-62e6-4cd7-a652-d631f9d77b54
  spec:
    sourcePod: network-check-source-6f8b768455-r7shg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T09:09:27Z"
      message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 982.741µs
      message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:09:27Z"
    - latency: 1.427033ms
      message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:08:27Z"
    - latency: 997.239µs
      message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:07:27Z"
    - latency: 1.521485ms
      message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:06:27Z"
    - latency: 1.196869ms
      message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:05:27Z"
    - latency: 973.116µs
      message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:04:27Z"
    - latency: 1.521286ms
      message: 'network-check-target-ip-10-0-132-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:03:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T09:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-66-to-network-check-target-ip-10-0-136-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-66.ec2.internal
      uid: 45fc4906-cb7d-4b4c-af18-4a5ab47375d9
    resourceVersion: "14406"
    uid: 704a3f94-c751-42ea-8f04-8c45bd5e6735
  spec:
    sourcePod: network-check-source-6f8b768455-r7shg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T09:09:27Z"
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.525675ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:09:27Z"
    - latency: 2.207566ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:08:27Z"
    - latency: 2.246945ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:07:27Z"
    - latency: 2.383132ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:06:27Z"
    - latency: 2.14541ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:05:27Z"
    - latency: 2.156575ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:04:27Z"
    - latency: 2.62071ms
      message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:03:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T09:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-66-to-network-check-target-ip-10-0-142-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-66.ec2.internal
      uid: 45fc4906-cb7d-4b4c-af18-4a5ab47375d9
    resourceVersion: "14407"
    uid: a70abb95-6297-482d-bd37-dec428461248
  spec:
    sourcePod: network-check-source-6f8b768455-r7shg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T09:09:27Z"
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.684257ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:09:27Z"
    - latency: 2.352035ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:08:27Z"
    - latency: 2.288613ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:07:27Z"
    - latency: 2.276481ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:06:27Z"
    - latency: 2.251422ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:05:27Z"
    - latency: 2.284442ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:04:27Z"
    - latency: 2.147846ms
      message: 'network-check-target-ip-10-0-142-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:03:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T09:02:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-66-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-66.ec2.internal
      uid: 45fc4906-cb7d-4b4c-af18-4a5ab47375d9
    resourceVersion: "14075"
    uid: 7add6b56-1c4c-4e76-8e4d-09cac90e413d
  spec:
    sourcePod: network-check-source-6f8b768455-r7shg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T09:08:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.416534ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:08:27Z"
    - latency: 2.099188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:08:27Z"
    - latency: 846.41µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:07:27Z"
    - latency: 1.666884ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:07:27Z"
    - latency: 864.911µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:06:27Z"
    - latency: 1.60777ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:06:27Z"
    - latency: 877.517µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:05:27Z"
    - latency: 1.83658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:05:27Z"
    - latency: 797.481µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T09:04:27Z"
    - latency: 2.05662ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T09:04:27Z"
kind: List
metadata:
  resourceVersion: ""