apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-198-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-198.ec2.internal
      uid: d991403d-e400-443f-913a-27bc14a305d8
    resourceVersion: "23743"
    uid: 490afe2e-e95a-4fd7-846e-15c5df906876
  spec:
    sourcePod: network-check-source-8894fc9bd-8hhzk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:54:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.023µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:54:54Z"
    - latency: 901.028µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:53:54Z"
    - latency: 848.276µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:52:54Z"
    - latency: 951.034µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:51:54Z"
    - latency: 1.006289ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:50:54Z"
    - latency: 1.539227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:49:54Z"
    - latency: 1.264622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-198-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-198.ec2.internal
      uid: d991403d-e400-443f-913a-27bc14a305d8
    resourceVersion: "22528"
    uid: c51c1cb0-a2e0-4d4a-8be9-52d85e1ebd15
  spec:
    sourcePod: network-check-source-8894fc9bd-8hhzk
    targetEndpoint: a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:53:54Z"
      message: 'load-balancer-api-external: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.870283ms
      message: 'load-balancer-api-external: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:53:54Z"
    - latency: 6.039782ms
      message: 'load-balancer-api-external: resolved host name a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:53:54Z"
    - latency: 4.330326ms
      message: 'load-balancer-api-external: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:52:54Z"
    - latency: 7.186318ms
      message: 'load-balancer-api-external: resolved host name a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:52:54Z"
    - latency: 5.085685ms
      message: 'load-balancer-api-external: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:51:54Z"
    - latency: 6.689038ms
      message: 'load-balancer-api-external: resolved host name a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:51:54Z"
    - latency: 4.341565ms
      message: 'load-balancer-api-external: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:50:54Z"
    - latency: 6.791864ms
      message: 'load-balancer-api-external: resolved host name a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:50:54Z"
    - latency: 5.760917ms
      message: 'load-balancer-api-external: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:49:54Z"
    - latency: 6.650389ms
      message: 'load-balancer-api-external: resolved host name a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:49:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-198-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-198.ec2.internal
      uid: d991403d-e400-443f-913a-27bc14a305d8
    resourceVersion: "22527"
    uid: e5af6175-e055-4a7a-81b0-cbf823d903dd
  spec:
    sourcePod: network-check-source-8894fc9bd-8hhzk
    targetEndpoint: a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:53:54Z"
      message: 'load-balancer-api-internal: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.808412ms
      message: 'load-balancer-api-internal: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:53:54Z"
    - latency: 5.977755ms
      message: 'load-balancer-api-internal: resolved host name a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:53:54Z"
    - latency: 4.288482ms
      message: 'load-balancer-api-internal: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:52:54Z"
    - latency: 7.166554ms
      message: 'load-balancer-api-internal: resolved host name a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:52:54Z"
    - latency: 5.05933ms
      message: 'load-balancer-api-internal: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:51:54Z"
    - latency: 6.720262ms
      message: 'load-balancer-api-internal: resolved host name a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:51:54Z"
    - latency: 4.353361ms
      message: 'load-balancer-api-internal: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:50:54Z"
    - latency: 6.761207ms
      message: 'load-balancer-api-internal: resolved host name a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:50:54Z"
    - latency: 5.810316ms
      message: 'load-balancer-api-internal: tcp connection to a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:49:54Z"
    - latency: 6.631137ms
      message: 'load-balancer-api-internal: resolved host name a4dfaeca9a3f344ce8b4c425c5d51287-fa0f91843b5057cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:49:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-198-to-network-check-target-ip-10-0-132-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-198.ec2.internal
      uid: d991403d-e400-443f-913a-27bc14a305d8
    resourceVersion: "23740"
    uid: b2ead4fc-c3f1-44a4-9035-c4b58b85c8b8
  spec:
    sourcePod: network-check-source-8894fc9bd-8hhzk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:54:54Z"
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.176613ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:54:54Z"
    - latency: 1.111571ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:53:54Z"
    - latency: 825.807µs
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:52:54Z"
    - latency: 872.068µs
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:51:54Z"
    - latency: 1.441744ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:50:54Z"
    - latency: 1.200447ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:49:54Z"
    - latency: 1.215967ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-198-to-network-check-target-ip-10-0-134-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-198.ec2.internal
      uid: d991403d-e400-443f-913a-27bc14a305d8
    resourceVersion: "23741"
    uid: 67897287-7b37-414a-92e3-01f6b4c6a6f3
  spec:
    sourcePod: network-check-source-8894fc9bd-8hhzk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:54:54Z"
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.018484ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:54:54Z"
    - latency: 1.695847ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:53:54Z"
    - latency: 1.925015ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:52:54Z"
    - latency: 2.037045ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:51:54Z"
    - latency: 1.967064ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:50:54Z"
    - latency: 1.892794ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:49:54Z"
    - latency: 2.140547ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-198-to-network-check-target-ip-10-0-135-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-198.ec2.internal
      uid: d991403d-e400-443f-913a-27bc14a305d8
    resourceVersion: "23742"
    uid: 6f15fd24-d3a8-4e16-93ff-d41cfaabddb1
  spec:
    sourcePod: network-check-source-8894fc9bd-8hhzk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:54:54Z"
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.428305ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:54:54Z"
    - latency: 1.9242ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:53:54Z"
    - latency: 1.976005ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:52:54Z"
    - latency: 2.282386ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:51:54Z"
    - latency: 2.400533ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:50:54Z"
    - latency: 2.931731ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:49:54Z"
    - latency: 2.383787ms
      message: 'network-check-target-ip-10-0-135-106: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:47:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-198-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-198.ec2.internal
      uid: d991403d-e400-443f-913a-27bc14a305d8
    resourceVersion: "22526"
    uid: e63be9f7-fa30-4716-bcc6-5bddca426d60
  spec:
    sourcePod: network-check-source-8894fc9bd-8hhzk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:53:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 674.587µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:53:54Z"
    - latency: 1.871628ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:53:54Z"
    - latency: 1.006561ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:52:54Z"
    - latency: 1.648611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:52:54Z"
    - latency: 1.204423ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:51:54Z"
    - latency: 1.735565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:51:54Z"
    - latency: 882.773µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:50:54Z"
    - latency: 1.46105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:50:54Z"
    - latency: 1.080692ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:49:54Z"
    - latency: 1.803369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:49:54Z"
kind: List
metadata:
  resourceVersion: ""