bfleming-ciena

from paramiko import SSHClient
from scp import SCPClient
 
def progress(filename, size, sent):
    print filename + " " + str(size) + " " + str(sent)
 
if __name__ == "__main__":
 
    ssh = SSHClient()
    ssh.load_system_host_keys()

bfleming-ciena

# Dumps all resources in all subscriptions and pulls fields related to the resource and most
# importantly, the tags currently applied.
#
# I was using this to import into an excel spreadsheet, which we then reviewed and modified the tag values.
# Then I would dump the spreadsheet back to csv and feed it into the python script which would go and
# update the tags.
echo "id,location,it_Environment,it_App,it_Role,it_Owner,name,resource group,kind,type,tags"
for i in $(az account list -o tsv|cut -f2); do
    az resource list --subscription="$i" | jq -r '.[] | [.id,.location,"","","","",.name,.resourceGroup,.kind,.type,(.tags | tostring)] | @csv'
done

bfleming-ciena

2019-04-18T18:00:09.690 [Information] Executing 'Functions.azure-auto-tag-creator' (Reason='This function was programmatically called via the host APIs.', Id=b265df84-a1cf-4fb2-b8bb-611c0d54b721)
2019-04-18T18:00:09.806 [Error] Executed 'Functions.azure-auto-tag-creator' (Failed, Id=b265df84-a1cf-4fb2-b8bb-611c0d54b721)
Result: Failure
Exception: ValueError: time data '9999-12-31T23:59:59.9999999+00:00' does not match format '%Y-%m-%dT%H:%M:%S.%fZ'
Stack:   File "/root/.pyenv/versions/3.6.8/lib/python3.6/site-packages/azure/functions_worker/dispatcher.py", line 273, in _handle__invocation_request
    pytype=pb_type_info.pytype)
  File "/root/.pyenv/versions/3.6.8/lib/python3.6/site-packages/azure/functions_worker/bindings/meta.py", line 296, in from_incoming_proto
    trigger_metadata=trigger_metadata)
  File "/root/.pyenv/versions/3.6.8/lib/python3.6/site-packages/azure/functions_worker/bindings/queue.py", line 89, in from_proto
    trigger_metadata, 'ExpirationTime'),

bfleming-ciena

~ module.vms_dmz_sqldmz.module.SQLDMZ1.azurerm_virtual_machine.vm-windows-with-datadisk
      boot_diagnostics.0.enabled:     "false" => "true"
      boot_diagnostics.0.storage_uri: "https://clustwitsqldmzdr77aa.blob.core.windows.net" => "https://clustwitsqldmzdr77aa.blob.core.windows.net/"


Running appy repeatedly finds the same change.

bfleming-ciena

#list metrics
aws --profile dev --region us-east-1 cloudwatch list-metrics --namespace "AWS/Billing"

# Estimated charges
aws --region us-east-1 cloudwatch get-metric-statistics  --namespace "AWS/Billing"  --metric-name "EstimatedCharges"  --dimension "Name=Currency,Value=USD"  --start-time $(gdate +"%Y-%m-%dT%H:%M:00" --date="-12 hours")  --end-time $(gdate +"%Y-%m-%dT%H:%M:00")  --statistic Maximum  --period 60  --output text | sort -r -k 3 | head -n 1 | cut -f 2

# Marketplace Charges
aws --profile dev --region us-east-1 cloudwatch get-metric-statistics  --namespace "AWS/Billing"  --metric-name "EstimatedCharges"  --dimensions Name=ServiceName,Value=AWSMarketplace Name=Currency,Value=USD   --start-time $(gdate +"%Y-%m-%dT%H:%M:00" --date="-12 hours")  --end-time $(gdate +"%Y-%m-%dT%H:%M:00")  --statistic Maximum  --period 60  --output text

# Redshift

bfleming-ciena

count = length(list)


lookup(list[count.index], "subscription_id") 

bfleming-ciena

Deployment

Update kube-apiserver (it is under the service kubernetes) in rancher via the UI.

click upgrade

Replace the command line with this. The IP range is my cluster IP range, yours could be different, just use what was there for you.

kube-apiserver --storage-backend=etcd2 --storage-media-type=application/json --service-cluster-ip-range=10.43.0.0/16 --etcd-servers=http://etcd.kubernetes.rancher.internal:2379 --insecure-bind-address=0.0.0.0 --insecure-port=0 --cloud-provider=rancher --allow_privileged=true --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,PersistentVolumeLabel,DefaultStorageClass,DefaultTolerationSeconds,ResourceQuota,MutatingAdmissionWebhook,ValidatingAdmissionWebhook --client-ca-file=/etc/kubernetes/ssl/ca.pem --tls-cert-file=/etc/kubernetes/ssl/cert.pem --tls-private-key-file=/etc/kubernetes/ssl/key.pem --kubelet-client-certificate=/etc/kubernetes/ssl/cert.pem --kubelet-client-key=/etc/kubernetes/ssl/key.pem --runtime-config=batch/v2alpha1 --anonymous-auth=false --a

bfleming-ciena

# Sorry for not mentioning the credit to the original author. I lost the original link. I just added the namespace to the picture.
function kube_context() {
    # could have used $?, but it was easier with a string compare
    local ctx=$(kubectl config current-context 2>&1)
    local ns=$(kubectl config get-contexts --no-headers | grep '*' | awk '{print $5}')

    if [ "${ctx}" != "error: current-context is not set" ]; then
        echo -n "<${ctx}:$ns> "
    fi
}

bfleming-ciena

-- My need was to include nodes outside of my k8s cluster for monitoring.
-- Thanks to @amalucelli for originally posting this.
-- https://github.com/coreos/prometheus-operator/issues/834
--
-- This is tested with k8s 1.9, and .17 prometheus operator, using the pre-built deployment at
-- https://github.com/coreos/prometheus-operator/blob/master/contrib/kube-prometheus/README.md
-- Steps: Deploy per the script above, and then apply these objects. Should appear in granfa after a short time.

kind: Service
apiVersion: v1

bfleming-ciena

gitfs_remotes:
  - http://ourrepo/repos/sxa/repo.git:
    - saltenv:
      - csdev:
        - ref: salt-csdev
        - root: 'salt/env'