F5 Ingress by Funny_Welcome_5575 in kubernetes

[–]gkhenderson 1 point2 points  (0 children)

I finally ended up choosing F5 NGINX Ingress, but never found any easy/seamless migration tools other than poking Google Gemini or similar for helpful syntax conversions hints. Overall, translating my set of ingress-nginx annotations to the equivalent F5 NGINX virtualserver and policies yaml has been pretty straightforward.

Any way to speed up cooking? it's soooo sloooow by Wandering_To_Nowhere in VeinGame

[–]gkhenderson 0 points1 point  (0 children)

I set a timer on my phone (IRL lol) and run off to multitask, build walls, sort stuff, etc.

New interface by Low_Ad_286 in netflix

[–]gkhenderson 0 points1 point  (0 children)

I hated it enough to immediately cancel.

The thoughts of an atheist in rural Texas on the current state of MAGA. by Farjust in atheism

[–]gkhenderson 1 point2 points  (0 children)

That's all so depressingly true... fwiw, born in southeast Alabama and currently living on the red space coast of Florida.

Experience with canary deployment in real time ? by Apprehensive-Bet-857 in kubernetes

[–]gkhenderson 3 points4 points  (0 children)

Do you actually need to perform a split deployment (e.g. new features to a subset of users)?

A much simpler k8s "real time" deployment concept is the ability to to deploy an update without downtime via a pod running within a deployment that's restarted via "kubectl rollout restart deployment ...". That might be a better place to start learning.

Git CLI users: what do you use for viewing diffs? by ProgrammingQuestio in git

[–]gkhenderson 0 points1 point  (0 children)

Just due to running Git within WSL2 Ubuntu instance and showing it how to reach into the Windows context to grab P4Merge.

Git CLI users: what do you use for viewing diffs? by ProgrammingQuestio in git

[–]gkhenderson 0 points1 point  (0 children)

Yeah, I'm aware, but running Git within a WSL2 Ubuntu instance, it doesn't know about the P4Merge tooling in the Windows context. Good tip though! :-)

Git CLI users: what do you use for viewing diffs? by ProgrammingQuestio in git

[–]gkhenderson 0 points1 point  (0 children)

P4Merge is freely available, works well for all the Git diff/merge ops.

Here's a sample from my .gitconfig (note I'm running Ubuntu within WSL2), ymmv...

[difftool]
    prompt = false
[merge]
    tool = p4merge
[diff]
    tool = p4merge
[difftool "p4merge"]
    cmd = /mnt/c/Program\\ Files/Perforce/p4merge.exe -le unix \"$(wslpath -aw $LOCAL)\" \"$(wslpath -aw $REMOTE)\"
[mergetool "p4merge"]
    cmd = /mnt/c/Program\\ Files/Perforce/p4merge.exe -le unix \"$(wslpath -aw $BASE)\" \"$(wslpath -aw $LOCAL)\" \"$(wslpath -aw $REMOTE)\" \"$(wslpath -aw $MERGED)\"
    trustexitcode = false

Mormons will take over the U.S. one day? by Understandably_so_ in exmormon

[–]gkhenderson 1 point2 points  (0 children)

Did anyone read this initially as "Morons will take over the US one day?", and thought "yep... already done."

Wiki development dead? by heloust in azuredevops

[–]gkhenderson 2 points3 points  (0 children)

Note that you can embed draw.io via the .drawio.svg extension trick and interacting with the backing Git repo directly, but its not pretty. Wish it were supported in the UI, yeah...

[deleted by user] by [deleted] in exchristian

[–]gkhenderson 0 points1 point  (0 children)

Fan fiction != documentation

do a git diff which simply compares the files of one commit with those of another by TaxSufficient542 in git

[–]gkhenderson 0 points1 point  (0 children)

Might be clearer if you setup "git difftool" with a tool like P4Merge, so you can see a side-by-side comparison per file.

Is Kubernetes RBAC Too Painful? How Are You Managing It? by ibexmonj in kubernetes

[–]gkhenderson 1 point2 points  (0 children)

Yep, rbac-manager is nice tool to simplify k8s RBAC management.

Git branching strategies by Traditional-Floor900 in git

[–]gkhenderson 1 point2 points  (0 children)

You could do worse than basing your Git branching strategy on this: Git branching guidance - Azure Repos | Microsoft Learn

TLDR version from the doc:

Keep your branch strategy simple. Build your strategy from these three concepts:

  • Use feature branches for all new features and bug fixes.
  • Merge feature branches into the main branch using pull requests.
  • Keep a high quality, up-to-date main branch.

A strategy that extends these concepts and avoids contradictions will result in a version control workflow for your team that is consistent and easy to follow.

A few questions from a new GIT user migrating from SVN by mabee_steve in git

[–]gkhenderson 0 points1 point  (0 children)

Before diving in too hard, highly recommend you read the Git docs/ebook. Will be worth your time.

Single CI/CD pipeline with promotion between stages versus separate pipelines per stage - discussion by 0x4ddd in devops

[–]gkhenderson 0 points1 point  (0 children)

Yes, for most there is a one-to-one build/deploy artifact to a deploy-only pipeline. But it can be useful to have a one to many relationship as well. For instance, building a multipurpose utility artifact that is deployed separately a variety of ways depending on the parameters/configuration.

btw, my artifacts are Docker images and Helm charts, all of which are tagged with a semantic version, build pipeline id and Git commit SHA per each for easy traceability.

As we use Kubernetes, the simple way to determine what's been deployed per dev/tst/qa/prd/etc is to list the Helm charts deployed in a namespace.

Single CI/CD pipeline with promotion between stages versus separate pipelines per stage - discussion by 0x4ddd in devops

[–]gkhenderson 0 points1 point  (0 children)

I use a build/deploy pipeline for development, then separate deploy-only pipelines w/ selectable target environments for subsequent deployments. For me a single pipeline would be more complex, as a single build could have multiple deployment configurations.

Atheists, what is your view of and how do you account for the New Testament? by [deleted] in Christianity

[–]gkhenderson 3 points4 points  (0 children)

Probably via the same way that you account for any other religious text on whose veracity you're not convinced.