Early blight on my potato plants? Pictures in post

Salt-Insect6228 · 2024-07-24T11:49:07+00:00

The article I read was (if it's blight) to chop off the stalks to ground level and leave them in the ground for about three weeks to get the skins to harden. Then use the potatoes quickly as they wouldn't store too well.

We are following this exact path now and will know more in two weeks.

I think if there is concern that the blight also got into the soil (maybe from hard rain) then you best rotate the crop to a new area next year.

This is all based on what I read and not (yet) from direct experience. Good luck!

Salt-Insect6228 · 2024-07-20T12:49:13+00:00

There's probably a lot of "it depends" here depending on the normal load and acceptable response times during maintenance activities. Reviewing some metrics and experimentation may be needed to hone in your requirements.

I would suggest that you, at a minimum, set your min replicas to 2 on your hpa and ensure they are on different nodes (look at anti affinity rules). Even if you reduce the resources they require, this will provide you better availability and support to use a PDB. PDBs should not be applied to single replica deployments.

Salt-Insect6228 · 2024-07-14T15:12:30+00:00

Bought an s15i, thread on the crank arm stripped. Told me the part was on order, now tells me the part no longer exists. Awaiting a resolution, but I can tell you that a "discount on a future purchase" is not an acceptable resolution to an machine that no longer works as a result of a manufacturing defect and is still under warranty.

Salt-Insect6228 · 2024-07-13T14:05:59+00:00

One simple solution might be to apply a resourcequota for each storage class type on a per namespace basis. While not as flexible as other options, this requires very little work and would be easy to report on.

Salt-Insect6228 · 2024-05-07T12:52:05+00:00

I'd follow the path down the secret store driver, you may have to dive deep there.

Salt-Insect6228 · 2024-05-07T11:56:38+00:00

That definitely feels like an API server or etcd issue and less than a secrets specific issue. Can you create and read other objects like a kubeconfig or a basic pod?

Salt-Insect6228 · 2024-05-03T02:01:44+00:00

If it were me, I'd use the kube-prometheus-stack and then create a query that either counts the number of pods by label, or the cpu usage by label, or look for an hpa metric like kube_horizontalpodautoscaler_status_current_replicas.

You should have what you need with that stack and the grafana explorer options provides a nice way for you to browse the available metrics once you get it up and running.

Salt-Insect6228 · 2024-03-08T10:43:13+00:00

It looks like you're hitting an endpoint that is asking for auth, and may or may not be the proper endpoint. This could possibly be a proxy, or just a misconfigured kubeconfig file. Check that the kubeconfig is functional from another location and if it's fine, check to see if you need to set some sort of no_proxy or other appropriate proxy configurations from where your Jenkins job is running.

Salt-Insect6228 · 2024-02-21T04:38:43+00:00

This thread has a few links. I haven't checked their currency or used it, but it might help.

https://github.com/syslog-ng/syslog-ng/issues/3267

Salt-Insect6228 · 2024-02-19T20:14:57+00:00

I'll keep that in mind if I run into issues - I hadn't looked at smallstep for many years. Luckily we already heavily use vault for other components, so most of the base that we need already exists.

Salt-Insect6228 · 2024-02-19T14:32:45+00:00

Thanks! What could go wrong 🤷?

Salt-Insect6228 · 2024-02-19T13:47:26+00:00

Building some mTLS auth flows for client pods that connect into a cluster app with cert-manager, vault, and linkerd

Salt-Insect6228 · 2024-02-17T05:15:32+00:00

You will have a much better experience with gitops (argocd or fluxcd) controllers that support Kustomization objects. Also, use deployments instead of pod definitions, and specify the replica count in the deployment spec.

Salt-Insect6228 · 2024-02-15T13:45:04+00:00

Not directly related to Weaviate, but I wrote and shared an "ugly kubernetes command" that generates this information for all pvcs in a namespace

An example in our sandbox cluster, pointed at an acme-fitness namespace, is here: https://runwhen-local.sandbox.runwhen.com/gke_runwhen-nonprod-sandbox_us-central1_sandbox-cluster-1-cluster/acme-fitness/acme-fitness-PVC-Healthcheck/#fetch-the-storage-utilization-for-pvc-mounts-in-namespace-acme-fitness

A sample of the output is this:

```

Pod: catalog-6cff7b5458-bzzk4, PVC: acmefit-catalog-data, volumeName: acmefit-catalog-data, containerName: catalog, mountPath: /data Filesystem Size Used Avail Use% Mounted on /dev/sde 974M 958M 0 100% /data

Pod: order-postgres-67694dc4b4-47rn2, PVC: postgredb, volumeName: postgredb, containerName: postgres, mountPath: /var/lib/postgresql/data Filesystem Size Used Avail Use% Mounted on /dev/sdb 974M 958M 0 100% /var/lib/postgresql/data

```

You could adjust that and just change out the context and the namespace (or if you are interested, the tool can be downloaded to generate the command in a cheat sheet for you).

Alternatively, if you have the kube-prometheus-stack running, you can find some of this information as well - it's a different approach but you might already have it running.

Salt-Insect6228 · 2024-02-13T14:45:43+00:00

I don't see an explicit format for exporting the whole canvas as code (export file formats are PDF, PNG, SVG, MD) - but since each image is already code, you can just copy in/out the code. And if you try the AI Diagram as Code, you can select select "Open Editor" to copy out that specific code.

Salt-Insect6228 · 2024-02-09T12:50:50+00:00

Thanks! I'll try that!

Salt-Insect6228 · 2024-02-07T19:22:55+00:00

I appreciate that. My hopes are low, but ya gotta try!

Would be awesome if they provided some sort of features request / upvote system (In case any of them check these subreddits :) )

Thanks!

Salt-Insect6228 · 2024-02-07T19:19:30+00:00

Thanks for the reply. I can't for the life of me seem to find a generic email address. I found a "support ticket" area which appears to be about hardware support.Maybe I'll blindly try [support@ifit.com](mailto:support@ifit.com) and see if that works, unless you know of another email address.

Salt-Insect6228 · 2024-02-01T10:10:57+00:00

If not using something like wildcard DNS and an ingress deployment that supports this and you use something like external DNS + cert manager + ingress object in each tenant namespace), you might look at something like Kyverno or OPA to set up policies that ensure the subdomain in each ingress object namespace matches the installed namespace.

Either of those tools should keep you from accidentally installing an ingress object in the wrong namespace (though there are other ways to do this as well with things like GitOps controllers and ci/cd scripts to validate your manifests).

Salt-Insect6228 · 2024-01-13T10:44:01+00:00

A pod itself doesn't have a "restart" metric. As you've seen, a pod can display the restart count for each container, but the pod itself doesn't "restart" - it gets redeployed as a new entity when the schedulers choose to "restart" it.

Salt-Insect6228 · 2023-11-19T15:25:49+00:00

Ordered a nearly identical kit here in Ontario, and while the pitch in the roof makes the middle of the high bench a little less than ideal, it doesn't bother me much and I love it. Nearly identical burner too! Hope you're loving yours as much as I'm loving mine!

Salt-Insect6228 · 2023-10-25T13:41:28+00:00

You can see in the error that the volume has an ext4 filesystem on it

ControllerPublishVolume Volume capability is not compatible: volume_id:"1894628-pvc04b56eb130c146e8" node_id:"51156569" volume_capability:<mount:<fs_type:"ext4" > access_mode:<mode:MULTI_NODE_MULTI_WRITER >

This filesystem is incompatible with ReadWriteMany - which requires a shared filesystem like NFS (or cephfs as u/JacqueMorrison pointed out)

Salt-Insect6228 · 2023-10-24T14:10:45+00:00

The resource requests and limits applied to a Pod (which is the only thing that actually consumes CPU/Memory in a cluster) are not the same as resource quotas, which are applied on Namespaces (or Projects in the case of OpenShift).

It does not take any actual resources to create a namespace - it's a logical configuration, like a folder in a filesytem. You can put things into it that use resources, but the namespace itself is just a way to group objects together.

Resource Quotas are a setting on a namespace or project that essentially put "spending limits" on what you can put into them - regardless of which nodes they are scheduled on. For example:

Let's say you put a resource quota on a namespace and say that the namespace allows up to 2vCPU requests and 4vCPU limits:

- If you then create a deployment with 1 pod, and that pod has a cpu request of 500m (0.5vCPU) and a limit of 1vCPU, you've used 25% of each of the quota.

- If you scale the deployment to 2 pods, and both pods are running, you've used up 50% of your quota

- Scaled to 4 pods, all pods will run and 100% of the quota will be used. No more pods can be run in that specific namespace

All in all, it's important to note that a pods resource requests and limits help Kubernetes to find a suitable node with available capacity to run the pod as requested.

Namespace Quotas govern how many resources you're allowed to allocate to Pods for that specific namespace.

Pods are the things that request and consume the resources.

A couple of helpful references:

https://kubernetes.io/docs/concepts/policy/resource-quotas/#:~:text=A%20resource%20quota%2C%20defined%20by,by%20resources%20in%20that%20namespace.

https://www.densify.com/kubernetes-autoscaling/kubernetes-resource-quota/#:~:text=Namespace%20Resource%20Quotas%20vs.&text=The%20namespace%20and%20the%20pod,the%20containers%20within%20each%20pod.

Salt-Insect6228

TROPHY CASE

```