apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:36:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-30-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-30.ec2.internal
      uid: 25bba5c6-6df6-44d7-a63f-098ce520379d
    resourceVersion: "24511"
    uid: 49075219-db26-40ab-8606-1b84a8702d44
  spec:
    sourcePod: network-check-source-56499946bc-ggv26
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:43:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.408847ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:43:13Z"
    - latency: 999.582µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:42:13Z"
    - latency: 1.229183ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:41:13Z"
    - latency: 1.400155ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:40:13Z"
    - latency: 1.248351ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:39:13Z"
    - latency: 856.089µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:38:13Z"
    - latency: 1.265583ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:37:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:36:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-30-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-30.ec2.internal
      uid: 25bba5c6-6df6-44d7-a63f-098ce520379d
    resourceVersion: "23302"
    uid: d7632f21-586a-4cfd-900c-5303c473cef5
  spec:
    sourcePod: network-check-source-56499946bc-ggv26
    targetEndpoint: a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:42:13Z"
      message: 'load-balancer-api-external: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.795825ms
      message: 'load-balancer-api-external: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:42:13Z"
    - latency: 7.598951ms
      message: 'load-balancer-api-external: resolved host name a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:42:13Z"
    - latency: 3.529735ms
      message: 'load-balancer-api-external: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:41:13Z"
    - latency: 8.585884ms
      message: 'load-balancer-api-external: resolved host name a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:41:13Z"
    - latency: 5.89535ms
      message: 'load-balancer-api-external: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:40:13Z"
    - latency: 8.362074ms
      message: 'load-balancer-api-external: resolved host name a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:40:13Z"
    - latency: 5.696937ms
      message: 'load-balancer-api-external: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:39:13Z"
    - latency: 8.140817ms
      message: 'load-balancer-api-external: resolved host name a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:39:13Z"
    - latency: 5.101175ms
      message: 'load-balancer-api-external: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:38:13Z"
    - latency: 15.76617ms
      message: 'load-balancer-api-external: resolved host name a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:38:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:36:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-30-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-30.ec2.internal
      uid: 25bba5c6-6df6-44d7-a63f-098ce520379d
    resourceVersion: "23301"
    uid: 251ae526-63db-49b5-a17a-c9186697eb37
  spec:
    sourcePod: network-check-source-56499946bc-ggv26
    targetEndpoint: a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:42:13Z"
      message: 'load-balancer-api-internal: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.648007ms
      message: 'load-balancer-api-internal: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:42:13Z"
    - latency: 7.677396ms
      message: 'load-balancer-api-internal: resolved host name a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:42:13Z"
    - latency: 4.267974ms
      message: 'load-balancer-api-internal: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:41:13Z"
    - latency: 8.529584ms
      message: 'load-balancer-api-internal: resolved host name a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:41:13Z"
    - latency: 5.211306ms
      message: 'load-balancer-api-internal: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:40:13Z"
    - latency: 8.26453ms
      message: 'load-balancer-api-internal: resolved host name a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:40:13Z"
    - latency: 5.678771ms
      message: 'load-balancer-api-internal: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:39:13Z"
    - latency: 8.167094ms
      message: 'load-balancer-api-internal: resolved host name a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:39:13Z"
    - latency: 5.037827ms
      message: 'load-balancer-api-internal: tcp connection to a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:38:13Z"
    - latency: 15.835155ms
      message: 'load-balancer-api-internal: resolved host name a40a52e2a4f724ba49041538df761d7f-3ec310c1f9bd091b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:38:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:36:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-30-to-network-check-target-ip-10-0-130-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-30.ec2.internal
      uid: 25bba5c6-6df6-44d7-a63f-098ce520379d
    resourceVersion: "24510"
    uid: fccd47de-8dae-48b9-9bf3-c4084e4db108
  spec:
    sourcePod: network-check-source-56499946bc-ggv26
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:43:13Z"
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.437334ms
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:43:13Z"
    - latency: 2.542394ms
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:42:13Z"
    - latency: 1.900859ms
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:41:13Z"
    - latency: 2.275794ms
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:40:13Z"
    - latency: 2.130385ms
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:39:13Z"
    - latency: 2.088968ms
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:38:13Z"
    - latency: 2.236817ms
      message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:37:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:36:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-30-to-network-check-target-ip-10-0-132-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-30.ec2.internal
      uid: 25bba5c6-6df6-44d7-a63f-098ce520379d
    resourceVersion: "24508"
    uid: 0c99daff-1b66-4b96-aa88-c15ded07ecbc
  spec:
    sourcePod: network-check-source-56499946bc-ggv26
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:43:13Z"
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 800.235µs
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:43:13Z"
    - latency: 837.999µs
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:42:13Z"
    - latency: 854.609µs
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:41:13Z"
    - latency: 1.095615ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:40:13Z"
    - latency: 721.527µs
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:39:13Z"
    - latency: 954.502µs
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:38:13Z"
    - latency: 1.151591ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:37:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:36:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-30-to-network-check-target-ip-10-0-135-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-30.ec2.internal
      uid: 25bba5c6-6df6-44d7-a63f-098ce520379d
    resourceVersion: "24509"
    uid: 16c2d7d2-8ec5-4ac8-9c00-2deb9b3b3a59
  spec:
    sourcePod: network-check-source-56499946bc-ggv26
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:43:13Z"
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.126537ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:43:13Z"
    - latency: 2.081926ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:42:13Z"
    - latency: 1.86866ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:41:13Z"
    - latency: 2.179238ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:40:13Z"
    - latency: 1.953369ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:39:13Z"
    - latency: 1.824718ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:38:13Z"
    - latency: 2.086995ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:37:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:36:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-30-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-30.ec2.internal
      uid: 25bba5c6-6df6-44d7-a63f-098ce520379d
    resourceVersion: "23300"
    uid: fb03ccfa-ca03-484b-9b1f-d521214f3e1d
  spec:
    sourcePod: network-check-source-56499946bc-ggv26
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:42:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 784.025µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:42:13Z"
    - latency: 1.658427ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:42:13Z"
    - latency: 836.688µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:41:13Z"
    - latency: 1.925159ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:41:13Z"
    - latency: 1.324755ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:40:13Z"
    - latency: 1.804257ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:40:13Z"
    - latency: 918.656µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:39:13Z"
    - latency: 1.910324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:39:13Z"
    - latency: 1.018208ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:38:13Z"
    - latency: 1.821844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:38:13Z"
kind: List
metadata:
  resourceVersion: ""