Skip to content

Instantly share code, notes, and snippets.

View skinny's full-sized avatar

Mark Gerrits skinny

  • Almere, Netherlands
View GitHub Profile
@skinny
skinny / README.md
Last active October 18, 2018 21:37 — forked from wildmichael/README.md
superscript test

this is a line of code formatted in just-in-casethis is here just-in-case

Azure Jumpbox (Amsterdam):
real 0m0.062s
user 0m0.016s
sys 0m0.004s
Belgie:
real 0m0.193s
user 0m0.011s
@skinny
skinny / exception.cs
Created April 25, 2018 13:09
SignalR core (preview2) exception when client disconnects.
[14:57:27 ERR] The remote party closed the WebSocket connection without completing the close handshake.
System.Net.WebSockets.WebSocketException (0x80004005): The remote party closed the WebSocket connection without completing the close handshake. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
--- End of inner exception stack trace ---
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.GetResult(Int16 token)
at System.Net.Http.HttpConnection.ReadBufferedAsyncCore(Memory`1 destination)
at System.Net.Http.HttpConnection.RawConnectionStream.ReadAsync(Memory`1 buffer, CancellationToken cancellationToken)
at System.Net.WebSockets.ManagedWebSocket.EnsureBufferContainsAsync(Int32 minimumRequiredBytes, Boo
apiVersion: v1
kind: Secret
metadata:
name: azure-secret
type: Opaque
data:
azurestorageaccountname: sxxxx==
azurestorageaccountkey: xxxxxx==
---
[
{
"title": "Book Title",
"content": "Lorum ipsum",
"chapters": [
{
"title": "Chapter 1",
"content": "Er was eens"
},
{
my relevant apimodel: ```{
"apiVersion": "vlabs",
"properties": {
"orchestratorProfile": {
"orchestratorType": "Kubernetes",
"orchestratorVersion": "1.9.3",
"kubernetesConfig": {
"networkPolicy": "calico",
"etcdDiskSizeGB": "64",
"useCloudControllerManager": true,
@skinny
skinny / readme.md
Last active February 23, 2018 09:27
Managing an `acs-engine` based Kubernetes cluster

How to update/modify an existing acs-engine based Kubernetes cluster

These steps describe how to change a running Kubernetes cluster deployed with acs-engine on Azure. These steps are only tested with changes targeting actually Azure resources. Changes made to Kubernetes configuration are not tested yet.

  • Modify the apimodel.json file located in the _output/<clustername> folder
  • Run acs-engine generate --api-model _output/<clustername>/apimodel.json. This wil update the azuredeploy* files needed for the new ARM deployment. These files are also located in the _output folder.
  • Apply the changes by manually starting an ARM deployment. From within the _output/<clustername> run az group deployment --template-file azuredeploy.json --parameters azuredeploy.parameters.json --resource-group "<my-resource-group>"
  • Grab a coffee
  • Profit!
VM TCP DUMP:
19:49:29.308741 IP 10.244.10.197.47602 > 10.244.7.40.domain: 41482+ A? nu.nl.default.svc.cluster.local. (49)
19:49:29.308795 IP 10.244.10.197.47602 > 10.244.7.40.domain: 3091+ AAAA? nu.nl.default.svc.cluster.local. (49)
19:49:29.312817 IP 10.244.7.40.domain > 10.244.10.197.47602: 3091 NXDomain 0/1/0 (124)
19:49:29.313044 IP 10.244.7.40.domain > 10.244.10.197.47602: 41482 NXDomain 0/1/0 (124)
19:49:29.313522 IP 10.244.10.197.40955 > 10.244.7.40.domain: 64695+ AAAA? nu.nl.svc.cluster.local. (41)
19:49:29.313525 IP 10.244.10.197.40955 > 10.244.7.40.domain: 36322+ A? nu.nl.svc.cluster.local. (41)
19:49:29.316305 IP 10.244.7.40.domain > 10.244.10.197.40955: 64695 NXDomain 0/1/0 (116)
@skinny
skinny / logs
Created January 17, 2018 19:34
VM TCP DUMP:
19:27:26.969454 IP 10.244.10.197.41060 > 10.244.7.38.domain: 30410+ A? nu.nl.default.svc.cluster.local. (49)
19:27:26.969454 IP 10.244.10.197.41060 > 10.244.7.38.domain: 48785+ AAAA? nu.nl.default.svc.cluster.local. (49)
19:27:26.973117 IP 10.244.7.38.domain > 10.244.10.197.41060: 30410 NXDomain 0/1/0 (124)
-- 5 sec timeout
19:27:31.973665 IP 10.244.10.197.41060 > 10.244.7.38.domain: 30410+ A? nu.nl.default.svc.cluster.local. (49)
CoreDNS log :
12432 - 10.244.10.4 - [15/Jan/2018:09:53:05 +0000] A IN nu.nl.default.svc.cluster.local. udp 49 false 512
25119 - 10.244.10.4 - [15/Jan/2018:09:53:05 +0000] AAAA IN nu.nl.default.svc.cluster.local. udp 49 false 512
44480 - 10.244.10.4 - [15/Jan/2018:09:53:05 +0000] A IN nu.nl.svc.cluster.local. udp 41 false 512
58983 - 10.244.10.4 - [15/Jan/2018:09:53:05 +0000] AAAA IN nu.nl.svc.cluster.local. udp 41 false 512
36288 - 10.244.10.4 - [15/Jan/2018:09:53:05 +0000] AAAA IN nu.nl.cluster.local. udp 37 false 512
23313 - 10.244.10.4 - [15/Jan/2018:09:53:05 +0000] A IN nu.nl.cluster.local. udp 37 false 512
55071 - 10.244.10.4 - [15/Jan/2018:09:53:05 +0000] A IN nu.nl. udp 23 false 512
55071 - 10.244.10.4 - [15/Jan/2018:09:53:10 +0000] A IN nu.nl. udp 23 false 512