rleap-m

#!/usr/bin/env bash
#
# fix-mke4-gateway-lb.sh
#
# After an MKE 3 -> MKE 4 migration, the MKE 4 NLB's :443 listener can end up
# pointed at the wrong gateway HTTPS NodePort. Symptom: the dashboard login
# succeeds in Dex but every API call returns 401 (OIDC issuer mismatch), and/or
# https://<lb-hostname>/ refuses the connection. Root cause: terraform wired the
# :443 listener to one NodePort (e.g. 33001) while mkectl deployed the envoy
# gateway on another (e.g. 33433, via --gateway-https-node-port).

rleap-m

mkectl apply — Windows Node Setup Sequence

MKE 4.2.0, WS2022.

#	Action	Observed
1	SSH connection established	HashKnownHosts=yes, keys hashed on connect
2	OS detection	uname | grep Linux, uname | grep Darwin both fail; falls through to Windows check
3	Windows confirmed	Get-CimInstance Win32_OperatingSystem → Microsoft Windows Server 2022 Datacenter 10.0.20348
4	Identity confirmed	whoami → ip-172-31-0-18\administrator; hostname → ip-172-31-0-18

rleap-m

<#
.Synopsis
 Renders a GMSA kubernetes resource manifest.
.DESCRIPTION
 This is me messing up the SHA value with a comment
#>
Param(
    [Parameter(Position = 0, Mandatory = $true)] [String] $AccountName,
    [Parameter(Position = 1, Mandatory = $true)] [String] $ResourceName,
    [Parameter(Position = 2, Mandatory = $false)] [String] $ManifestFile,

rleap-m

#!/usr/bin/env bash
#
# Mirantis Container Runtime installer
#
# Script build information:
# COMMIT_SHA=thisisafakeshamadebyrleap
# COMMIT_SHA_PVAL=thisisa
# SEMVER_VERSION=1.0.25
# PUBLISH_STRING=test

rleap-m

#!/usr/bin/env bash
set -euo pipefail

SCRIPT_NAME="$(basename "$0")"
VERSION="1.0.0"

usage() {
  cat <<EOF
Usage:
  ${SCRIPT_NAME} <command> [options]

rleap-m

<#
.SYNOPSIS
    Utility script to create a Terraform working directory from a repository
.EXAMPLE
    Copy-QaInfra.ps1 -VariablePath ./mke_412_rc1 -DestinationPath ./mke_412_ga -Verbose
#>
[CmdletBinding()]
param (
    # Path to the items to copy
    [ValidateScript({Test-Path $_ -PathType Container})]

rleap-m

<#
.SYNOPSIS
    Gets AWS VPC peering connections
.DESCRIPTION
    Sometimes we use peering connections to connect VPCs (especially convenient to allow an MKE
    cluster to reach an LDAP server
.PARAMETER Region
    AWS region where the VPCs reside
.NOTES
    Author - rleap@mirantis.com

rleap-m

#!/usr/bin/env bash
set -euo pipefail

# ============================================
# MKE / Dex OAuth2 PKCE token fetcher (bash-only)
# - Auth Code + PKCE: interactive (copy/paste code)
# - Refresh grant: non-interactive
#
# deps: bash, curl, openssl, base64, tr, sed
# (jq optional; script falls back to sed)

rleap-m

#!/bin/bash

# Defaults (can be overridden by CLI flags)
HARBOR_URL="${HARBOR_URL:-}"
HARBOR_USER="${HARBOR_USER:-}"
HARBOR_PWD="${HARBOR_PWD:-}"
PREFIX="migration-rule-"
PAGE_SIZE=100
MODE="all"
LATEST_ONLY="false"

rleap-m

#!/bin/bash
set -euo pipefail

PAGE_SIZE=100

# Default values from environment, can be overridden via CLI
HARBOR_URL="${HARBOR_URL:-}"
HARBOR_USER="${HARBOR_USER:-}"
HARBOR_PWD="${HARBOR_PWD:-}"
DRY_RUN=false