apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T09:43:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 88b42995-0bb3-45f5-9477-dca61df1497b
    resourceVersion: "16336"
    uid: 6daf5803-f2c8-4187-b2dc-cfafd3dacf5f
  spec:
    sourcePod: network-check-source-dbd9cf844-6vwr7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T09:50:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.06081ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:50:40Z"
    - latency: 1.013855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:49:40Z"
    - latency: 1.068616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:48:40Z"
    - latency: 1.352718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:47:40Z"
    - latency: 880.111µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:46:40Z"
    - latency: 1.324916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:45:40Z"
    - latency: 926.516µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:44:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T09:43:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 88b42995-0bb3-45f5-9477-dca61df1497b
    resourceVersion: "15985"
    uid: e6be5c45-1e52-4fd9-93e4-bd4561d5f7b8
  spec:
    sourcePod: network-check-source-dbd9cf844-6vwr7
    targetEndpoint: a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T09:49:40Z"
      message: 'load-balancer-api-external: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.700175ms
      message: 'load-balancer-api-external: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:49:40Z"
    - latency: 7.849698ms
      message: 'load-balancer-api-external: resolved host name a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:49:40Z"
    - latency: 4.826705ms
      message: 'load-balancer-api-external: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:48:40Z"
    - latency: 8.408532ms
      message: 'load-balancer-api-external: resolved host name a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:48:40Z"
    - latency: 5.090745ms
      message: 'load-balancer-api-external: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:47:40Z"
    - latency: 9.548309ms
      message: 'load-balancer-api-external: resolved host name a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:47:40Z"
    - latency: 4.637351ms
      message: 'load-balancer-api-external: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:46:40Z"
    - latency: 16.00797ms
      message: 'load-balancer-api-external: resolved host name a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:46:40Z"
    - latency: 12.773473ms
      message: 'load-balancer-api-external: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:45:40Z"
    - latency: 12.724691ms
      message: 'load-balancer-api-external: resolved host name a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:45:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T09:43:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 88b42995-0bb3-45f5-9477-dca61df1497b
    resourceVersion: "15984"
    uid: 65de578d-e7fa-4cf4-9071-64b279e7b84d
  spec:
    sourcePod: network-check-source-dbd9cf844-6vwr7
    targetEndpoint: a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T09:49:40Z"
      message: 'load-balancer-api-internal: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.609674ms
      message: 'load-balancer-api-internal: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:49:40Z"
    - latency: 7.795474ms
      message: 'load-balancer-api-internal: resolved host name a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:49:40Z"
    - latency: 4.894905ms
      message: 'load-balancer-api-internal: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:48:40Z"
    - latency: 8.374503ms
      message: 'load-balancer-api-internal: resolved host name a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:48:40Z"
    - latency: 5.126973ms
      message: 'load-balancer-api-internal: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:47:40Z"
    - latency: 9.449015ms
      message: 'load-balancer-api-internal: resolved host name a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:47:40Z"
    - latency: 4.647519ms
      message: 'load-balancer-api-internal: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:46:40Z"
    - latency: 15.92518ms
      message: 'load-balancer-api-internal: resolved host name a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:46:40Z"
    - latency: 4.579832ms
      message: 'load-balancer-api-internal: tcp connection to a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:45:40Z"
    - latency: 12.684265ms
      message: 'load-balancer-api-internal: resolved host name a3a76a7f215b141dea5083933b6e03fa-e1328804db549688.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:45:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T09:43:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-network-check-target-ip-10-0-131-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 88b42995-0bb3-45f5-9477-dca61df1497b
    resourceVersion: "16333"
    uid: 2bdd472b-815b-43a1-b67b-3bc841313bb7
  spec:
    sourcePod: network-check-source-dbd9cf844-6vwr7
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T09:50:40Z"
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 785.199µs
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:50:40Z"
    - latency: 1.245278ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:49:40Z"
    - latency: 789.753µs
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:48:40Z"
    - latency: 1.352915ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:47:40Z"
    - latency: 885.392µs
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:46:40Z"
    - latency: 796.894µs
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:45:40Z"
    - latency: 1.224912ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:44:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T09:43:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-network-check-target-ip-10-0-138-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 88b42995-0bb3-45f5-9477-dca61df1497b
    resourceVersion: "16335"
    uid: 26ad3a42-31e9-4a41-a1c6-e7855baf6a0a
  spec:
    sourcePod: network-check-source-dbd9cf844-6vwr7
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T09:50:40Z"
      message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.239588ms
      message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:50:40Z"
    - latency: 1.882952ms
      message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:49:40Z"
    - latency: 2.231659ms
      message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:48:40Z"
    - latency: 2.047411ms
      message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:47:40Z"
    - latency: 2.227406ms
      message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:46:40Z"
    - latency: 2.215859ms
      message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:45:40Z"
    - latency: 2.235911ms
      message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:44:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T09:43:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-network-check-target-ip-10-0-140-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 88b42995-0bb3-45f5-9477-dca61df1497b
    resourceVersion: "16334"
    uid: 9a487ad8-5379-4880-b405-45f45d43f3e7
  spec:
    sourcePod: network-check-source-dbd9cf844-6vwr7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T09:50:40Z"
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.983353ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:50:40Z"
    - latency: 1.982305ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:49:40Z"
    - latency: 2.040622ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:48:40Z"
    - latency: 1.972774ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:47:40Z"
    - latency: 2.01328ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:46:40Z"
    - latency: 1.955822ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:45:40Z"
    - latency: 2.010258ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:44:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T09:43:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 88b42995-0bb3-45f5-9477-dca61df1497b
    resourceVersion: "15983"
    uid: dfbf7a28-6b0f-496b-b9da-fc599e3c6acd
  spec:
    sourcePod: network-check-source-dbd9cf844-6vwr7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T09:49:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 905.837µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:49:40Z"
    - latency: 1.993877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:49:40Z"
    - latency: 1.134723ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:48:40Z"
    - latency: 1.828139ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:48:40Z"
    - latency: 911.749µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:47:40Z"
    - latency: 2.044272ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:47:40Z"
    - latency: 1.204609ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:46:40Z"
    - latency: 1.833542ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:46:40Z"
    - latency: 1.115379ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T09:45:40Z"
    - latency: 1.518903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T09:45:40Z"
kind: List
metadata:
  resourceVersion: ""