apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:56:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: ef80f93a-8b7a-4b3b-89ae-4b17d2286d70
    resourceVersion: "11891"
    uid: 946eab1b-6cc7-4086-8bc1-3502960b5ce2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-d9x7k
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: ef80f93a-8b7a-4b3b-89ae-4b17d2286d70
    resourceVersion: "15503"
    uid: a718f0e9-bd12-4de1-9281-f0451b8f480f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-d9x7k
    targetEndpoint: ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T08:02:07Z"
      message: 'load-balancer-api-external: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.082031ms
      message: 'load-balancer-api-external: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:02:07Z"
    - latency: 10.06945ms
      message: 'load-balancer-api-external: resolved host name ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T08:02:07Z"
    - latency: 4.199174ms
      message: 'load-balancer-api-external: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:01:07Z"
    - latency: 8.413446ms
      message: 'load-balancer-api-external: resolved host name ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T08:01:07Z"
    - latency: 4.806511ms
      message: 'load-balancer-api-external: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:00:07Z"
    - latency: 8.531616ms
      message: 'load-balancer-api-external: resolved host name ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T08:00:07Z"
    - latency: 5.165515ms
      message: 'load-balancer-api-external: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:59:07Z"
    - latency: 9.290823ms
      message: 'load-balancer-api-external: resolved host name ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:59:07Z"
    - latency: 4.26797ms
      message: 'load-balancer-api-external: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:58:07Z"
    - latency: 8.266767ms
      message: 'load-balancer-api-external: resolved host name ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:58:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: ef80f93a-8b7a-4b3b-89ae-4b17d2286d70
    resourceVersion: "15502"
    uid: 6386c949-7ae5-4592-bcbb-13d63ff1ed10
  spec:
    sourcePod: network-check-source-7bc5b6bf85-d9x7k
    targetEndpoint: ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T08:02:07Z"
      message: 'load-balancer-api-internal: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.670378ms
      message: 'load-balancer-api-internal: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:02:07Z"
    - latency: 10.144737ms
      message: 'load-balancer-api-internal: resolved host name ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T08:02:07Z"
    - latency: 4.224566ms
      message: 'load-balancer-api-internal: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:01:07Z"
    - latency: 8.50588ms
      message: 'load-balancer-api-internal: resolved host name ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T08:01:07Z"
    - latency: 5.350363ms
      message: 'load-balancer-api-internal: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:00:07Z"
    - latency: 8.454612ms
      message: 'load-balancer-api-internal: resolved host name ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T08:00:07Z"
    - latency: 5.153226ms
      message: 'load-balancer-api-internal: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:59:07Z"
    - latency: 9.350359ms
      message: 'load-balancer-api-internal: resolved host name ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:59:07Z"
    - latency: 4.234608ms
      message: 'load-balancer-api-internal: tcp connection to ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:58:07Z"
    - latency: 8.34437ms
      message: 'load-balancer-api-internal: resolved host name ad33b601f3c5349abadc8caa9fec10d3-c95dca5d55a4a553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:58:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:56:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-network-check-target-ip-10-0-130-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: ef80f93a-8b7a-4b3b-89ae-4b17d2286d70
    resourceVersion: "11890"
    uid: f2605ed9-f89a-4754-88e9-b4de233e521a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-d9x7k
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:56:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-network-check-target-ip-10-0-131-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: ef80f93a-8b7a-4b3b-89ae-4b17d2286d70
    resourceVersion: "11888"
    uid: 47707c82-7dc7-4d15-a77c-b3bd1923cdf8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-d9x7k
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:56:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-network-check-target-ip-10-0-131-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: ef80f93a-8b7a-4b3b-89ae-4b17d2286d70
    resourceVersion: "11887"
    uid: 8d3e4c83-b003-4b76-b72b-b657d110035e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-d9x7k
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T07:56:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: ef80f93a-8b7a-4b3b-89ae-4b17d2286d70
    resourceVersion: "15498"
    uid: 805e90f9-46f8-4245-bcfa-2f891f43c7cb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-d9x7k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T08:02:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 810.421µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:02:07Z"
    - latency: 2.246609ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T08:02:07Z"
    - latency: 891.393µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:01:07Z"
    - latency: 1.753969ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T08:01:07Z"
    - latency: 857.029µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T08:00:07Z"
    - latency: 1.609363ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T08:00:07Z"
    - latency: 1.04014ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:59:07Z"
    - latency: 1.555887ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:59:07Z"
    - latency: 945.149µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:58:07Z"
    - latency: 1.683754ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:58:07Z"
kind: List
metadata:
  resourceVersion: ""