apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 87340ecc-46b9-4578-95a5-2b7c18cc8e19
    resourceVersion: "14580"
    uid: b5b50ec9-182a-4388-b2b0-f017e866c284
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkhjp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:09:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.01171ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:43Z"
    - latency: 1.060786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:43Z"
    - latency: 981.411µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:43Z"
    - latency: 1.04736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:43Z"
    - latency: 1.063159ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:43Z"
    - latency: 1.100622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:43Z"
    - latency: 1.055445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 87340ecc-46b9-4578-95a5-2b7c18cc8e19
    resourceVersion: "14222"
    uid: a3dbe695-6bb9-4e62-a3bb-e38ea061e471
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkhjp
    targetEndpoint: a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:43Z"
      message: 'load-balancer-api-external: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.171894ms
      message: 'load-balancer-api-external: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:43Z"
    - latency: 9.168183ms
      message: 'load-balancer-api-external: resolved host name a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:08:43Z"
    - latency: 6.353625ms
      message: 'load-balancer-api-external: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:43Z"
    - latency: 7.858262ms
      message: 'load-balancer-api-external: resolved host name a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:07:43Z"
    - latency: 2.82575ms
      message: 'load-balancer-api-external: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:43Z"
    - latency: 9.633412ms
      message: 'load-balancer-api-external: resolved host name a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:43Z"
    - latency: 3.54756ms
      message: 'load-balancer-api-external: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:43Z"
    - latency: 9.62926ms
      message: 'load-balancer-api-external: resolved host name a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:43Z"
    - latency: 4.14418ms
      message: 'load-balancer-api-external: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:43Z"
    - latency: 6.439308ms
      message: 'load-balancer-api-external: resolved host name a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 87340ecc-46b9-4578-95a5-2b7c18cc8e19
    resourceVersion: "14223"
    uid: fab28009-bda2-4ed6-940b-a1f90c74036c
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkhjp
    targetEndpoint: a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:43Z"
      message: 'load-balancer-api-internal: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.164846ms
      message: 'load-balancer-api-internal: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:43Z"
    - latency: 9.27027ms
      message: 'load-balancer-api-internal: resolved host name a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:08:43Z"
    - latency: 6.345236ms
      message: 'load-balancer-api-internal: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:43Z"
    - latency: 7.866775ms
      message: 'load-balancer-api-internal: resolved host name a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:07:43Z"
    - latency: 2.940806ms
      message: 'load-balancer-api-internal: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:43Z"
    - latency: 9.593665ms
      message: 'load-balancer-api-internal: resolved host name a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:43Z"
    - latency: 4.256831ms
      message: 'load-balancer-api-internal: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:43Z"
    - latency: 9.603679ms
      message: 'load-balancer-api-internal: resolved host name a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:43Z"
    - latency: 4.11935ms
      message: 'load-balancer-api-internal: tcp connection to a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:43Z"
    - latency: 6.506267ms
      message: 'load-balancer-api-internal: resolved host name a7196ebff373f4089a65f25c26a2089c-9d2258db056b3ba6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-network-check-target-ip-10-0-129-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 87340ecc-46b9-4578-95a5-2b7c18cc8e19
    resourceVersion: "14579"
    uid: 4b323cb0-fbb2-4bf7-896b-c61171f03747
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkhjp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:09:43Z"
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.203071ms
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:43Z"
    - latency: 2.273818ms
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:43Z"
    - latency: 2.224525ms
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:43Z"
    - latency: 2.300876ms
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:43Z"
    - latency: 2.558489ms
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:43Z"
    - latency: 2.148391ms
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:43Z"
    - latency: 2.181923ms
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-network-check-target-ip-10-0-132-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 87340ecc-46b9-4578-95a5-2b7c18cc8e19
    resourceVersion: "14578"
    uid: b79b0119-fa63-4c7b-b6ce-e78270fe4796
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkhjp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:09:43Z"
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.287005ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:43Z"
    - latency: 2.476571ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:43Z"
    - latency: 2.402569ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:43Z"
    - latency: 2.257429ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:43Z"
    - latency: 2.402584ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:43Z"
    - latency: 2.590183ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:43Z"
    - latency: 2.708843ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-network-check-target-ip-10-0-139-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 87340ecc-46b9-4578-95a5-2b7c18cc8e19
    resourceVersion: "14577"
    uid: 932a535c-bd9e-4324-925e-722233d109bb
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkhjp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:09:43Z"
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.447µs
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:43Z"
    - latency: 1.130956ms
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:43Z"
    - latency: 1.412323ms
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:43Z"
    - latency: 1.166559ms
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:43Z"
    - latency: 952.591µs
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:43Z"
    - latency: 919.447µs
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:43Z"
    - latency: 1.566777ms
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 87340ecc-46b9-4578-95a5-2b7c18cc8e19
    resourceVersion: "14221"
    uid: c846c2bc-7f15-4757-86d7-5bbf4d12a532
  spec:
    sourcePod: network-check-source-7d88cb55d8-wkhjp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.002807ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:43Z"
    - latency: 1.531263ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:08:43Z"
    - latency: 978.33µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:43Z"
    - latency: 2.095317ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:07:43Z"
    - latency: 894.672µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:43Z"
    - latency: 1.866524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:43Z"
    - latency: 1.030386ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:43Z"
    - latency: 1.667324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:43Z"
    - latency: 926.039µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:43Z"
    - latency: 1.655389ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:43Z"
kind: List
metadata:
  resourceVersion: ""