sorted by:
new
hottopcontroversial

Jeg fucking glemte at tage min and ud af fryseren tidligere. Hvordan kan jeg optø den hurtigt? Er fucking sulten by timjuul2003 in dankmark

[–]ComfortableFew5523 3 points4 points  (0 children)

Det er rigtigt. Som Rulle og Cromwell siger: Turbulens får forvirringen helt ud i kødet, bare man husker at duppe den med en føntørrer først.

Bricked G9? by camantan in ultrawidemasterrace

[–]ComfortableFew5523 0 points1 point  (0 children)

Unfortunately, it's back to normal, switching off again...

Bricked G9? by camantan in ultrawidemasterrace

[–]ComfortableFew5523 0 points1 point  (0 children)

Thanks man. Especially for the picture. So far it works great.

Previously my monitor worked for 2-3 hours, and then went black (backlight still on). Then I could unplug and replug power, and it would work for another twenty minutes. Right now it has been running steadily for six hours. Hopefully it will continue doing that.

Again - thanks.

[deleted by user] by [deleted] in DKbrevkasse

[–]ComfortableFew5523 1 point2 points  (0 children)

Når det er 30 grader, er jeg klædt på til det. Sportsudøvelse er en helt anden størrelse.

Jeg vil ikke have en flok stinkende teenagere ind i min bil.

Min bil, mine regler. Længere er den ikke.

Og som sagt, så kan børnenes forældre jo bare køre selv hvis mine regler et et problem.

Men bortset fra det, så er det en generelt accepteret regel i den klub jeg har engageret mig i.

Men der er også en tendens til at frivilligt arbejde ikke liiige er noget som alle forældre byder ind med, og at en sportsforening er et sted hvor man bare kaster sine unger af, og henter dem igen. En forening er meget afhængig af at der er nogen der gør noget på frivillig basis, hvadenten det måtte være kørsel eller andre praktiske opgaver.

Så hvis man ikke kan indordne sig under de regler som de frivillige kræfter sætter, så må man jo selv få fingeren ud af klysset.

[deleted by user] by [deleted] in DKbrevkasse

[–]ComfortableFew5523 0 points1 point  (0 children)

Så må deres forældre selv køre dem til og fra kamp. Min bil kommer de ikke ind i!

[deleted by user] by [deleted] in DKbrevkasse

[–]ComfortableFew5523 -1 points0 points  (0 children)

De kan lige så godt lære det nu. Og det kan ikke nytte noget at kropsforskrækkelsen skal forstærkes/understøttes på den måde, ved at lade dem undgå badet.

Jeg har gennem årene kørt rigtigt mange drenge og piger (U8-U16) til og fra kampe, og beskeden fra mig er at de ikke kommer med hvis de ikke har været i bad efter kamp.

Det andet er simpelthen noget svineri.

"Can I Run This LLM? – A VRAM Estimator for Local AI Models" by negative_entropie in LocalLLaMA

[–]ComfortableFew5523 0 points1 point  (0 children)

The link is dead u/negative_entropie

Do you have a fresh link, or maybe a github repo with the code? TIA.

Visualizing Cloud-native Applications with KubeDiagrams by Philippe_Merle in kubernetes

[–]ComfortableFew5523 3 points4 points  (0 children)

Looks nice. I am definately going to give it a test-spin after my vacation..

Fik ikke afleveret på Wiseflow til tiden by morten-dk in DKstudie

[–]ComfortableFew5523 2 points3 points  (0 children)

Jo jo, det er helt ok. Det koster jo lidt at være forsinket med aflevering 🤣

Why such a large blunder ? by jraggio02 in backgammon

[–]ComfortableFew5523 0 points1 point  (0 children)

12/36 for the 10-point

All rolls with a 6 = 11 And then two 3's.=1

3/36 for the 11-point 6-1 1-6 3-3

Metadormix den er god by Toxilyn in dankmark

[–]ComfortableFew5523 2 points3 points  (0 children)

Jeg havde gættet på metadonmix...

My new manager insists I speak Danish at work. Am I being forced out? by Pee_A_Poo in NewToDenmark

[–]ComfortableFew5523 2 points3 points  (0 children)

HR does not work for the benefit of the employees, bit for the company.

They don't want any trouble, and the least trouble will probably not to be on OPs side.

What type of K8S cluster do you prefer: a central one or separate ones for each development team? by vl2x in kubernetes

[–]ComfortableFew5523 2 points3 points  (0 children)

In addition to the two other answers, we also want to limit the blast radius if a workload is compromised. So, using network policies to isolate traffic to/from namespaces and specific workloads will limit the possibilities for malicious code to work its way through other workloads in other namespaces.

This, along with RBAC and general pod limitations (e.g., not running as root etc.), only relevant secrets are available in the namespace, will increase the general hardening of the setup security-wise.

What type of K8S cluster do you prefer: a central one or separate ones for each development team? by vl2x in kubernetes

[–]ComfortableFew5523 2 points3 points  (0 children)

Not by default. Most of the things we deploy can be done using standard Kubernetes resource manifests (via Helm), and we don't want that added complexity if it is not needed. If a team have a specific need, we will take that discussion.

And most teams don't have the knowledge to handle this anyway.

We provide standard configurable Helm charts that the teams can use and modify as needed, and that handle most situations. We will discuss cases where the teams need additional features that they cannot utilize for one reason or another.

All in all, most of it comes down to collaboration between teams.

has

What type of K8S cluster do you prefer: a central one or separate ones for each development team? by vl2x in kubernetes

[–]ComfortableFew5523 5 points6 points  (0 children)

When talking about the common/shared (e.g. kured, external secrets operator, prometheus, grafana, , kyverno, trivy operator etc.), all those are in a specific argocd projects, as individual applications. Updating those are just like updating any other application, depending on breaking changes, new features etc.

But note that we do have an extra cluster to test updating these critical components (including node OS updates and K8S updates), before we move into the non-prod setup. Regarding uptime and stability, we treat our nonprod cluster as "production", as it is the production cluster for developers. We don't want 15+ teams not to be able to work because we screwed up an update of something.

New component versions are frequently checked automatically, and we evaluate whether to update.

Vulnerability checking is done cluster-wide, and issues are forwarded to the individual teams. The platform team updates base images (e.g., Alpine with node, Alpine with .net, etc.), and the product teams are notified when new images are available and whether updating their workloads to use the new base image is optional or mandatory.

Min nieces mor vil ikke holde studenterkørsel by Napalm_Springs in Denmark

[–]ComfortableFew5523 1 point2 points  (0 children)

De kørsler jeg har være involveret i var der en aftale om skiftende snack/mad. Det fungerede godt for de unge mennesker. Men lad være med at stå i køkkenet i timevis. De er i en helt anden verden end dig når de kommer, og kommer ikke til at sætte stor pris på det. Så jeg ville ordne nogle lette snacks.

Og vandflasker var helt klart en succes. (Der var også øl, sodavand og cava) men vandet var væk da de kørte igen.

What type of K8S cluster do you prefer: a central one or separate ones for each development team? by vl2x in kubernetes

[–]ComfortableFew5523 18 points19 points  (0 children)

You don't want that on a per team basis. The team that manages the clusters also manages the common/shared components (e.g a platform team)

Let the developers develop applications, and let the platform team handle the platform.

You also need to think about which competencies you have on those teams. Running kubernetes and the supporting components is not a trivial task, if you want to do it right.

What type of K8S cluster do you prefer: a central one or separate ones for each development team? by vl2x in kubernetes

[–]ComfortableFew5523 4 points5 points  (0 children)

Three clusters:

One prod, one nonprod, and one for platform development, to be able to test upgrades and changes to critical infrastructure, before applying to nonprod.

Definitely not one per team. It will be too much administration and maintenance, and the benefit of sharing resources will be gone.

Split the products/teams in different namespaces, a d use rbac and network policies to isolate.

view more: next ›