Fixes and small improvements

Customizable status progress period

Configured with option MultitrackOptions.StatusProgressPeriod.

Default multitrack status-progress-period=5sec, -1 to disable status-progress

Ignore 'POST operation could not be complete' sts errors

Improve status progress and log chunks view

• Add line between log chunks
• Common column sizes for all resources
• Union "SUCCEEDED", "FAILED" fields for JOB
• Reject AGE collumn for POD and JOB kinds

Suppress k8s.io/klog INFO and WARNING streams

These streams print unnecessary service messages from underlying libraries.

Support kubernetes 1.16.0

Installation

Linux amd64

Darwin amd64

Windows amd64

SHA256SUMS

Fix broken output

Fix broken output

1. Fix broken output when running kubedog inside interactive docker run -ti container

• Terminal width is forced to default 140 symbols, can be forced with env var KUBEDOG_TERMINAL_WIDHT=N.
• Kubedog output is always colorized, can be disabled with KUBEDOG_NO_COLOR=1.

2. Fix kubedog version always gives dev.

Installation

Linux amd64

Darwin amd64

Windows amd64

SHA256SUMS

More tracking modes and some fixes

"Do not wait till resource is done" termination mode support

There are 2 TrackTerminationMode-s:

1. WaitUntilResourceReady — default, track this resource until it is ready.
2. NonBlocking — track resource only until there are other running resources trackers.

More logs modes

• ShowServiceMessages mode implemented (false by default): show kubernetes events and other kube service messages in realtime during tracking.
• SkipLogs multitracker spec mode implemented.

Fixes

• Show jobs logs in multitrack till pods are gone.
• Fix sts tracker hangs on kubernetes 1.10;
• Fix multitrack logs.

Installation

Linux amd64

Darwin amd64

Windows amd64

SHA256SUMS

Cli '--output-prefix' option; improve multitracker output

• kubedog multitrack --output-prefix option to set arbitrary prefix for kubedog output.
• Do not print excess newlines when resources are ready immediately.
• Fix multitracker does not show StatefulSet's and DaemonSet's Pods logs.
• Show logs of all Pods till pod reaches ready state (not configurable for now).

Installation

Linux amd64

Darwin amd64

Windows amd64

SHA256SUMS

Introducing Multitracker!

Introducing Multitracker!

Multitracker aimed to track multiple resources at the same time. Resources configured using MultitrackSpecs structure:

type MultitrackSpecs struct {
        Deployments  []MultitrackSpec
        StatefulSets []MultitrackSpec
        DaemonSets   []MultitrackSpec
        Jobs         []MultitrackSpec
}

Each resource is specified using MultitrackSpec structure:

type MultitrackSpec struct {
        ResourceName string
        Namespace    string

        FailMode                FailMode
        AllowFailuresCount      *int
        FailureThresholdSeconds *int

        LogRegex                *regexp.Regexp
        LogRegexByContainerName map[string]*regexp.Regexp

        SkipLogs                  bool
        SkipLogsForContainers     []string
        ShowLogsOnlyForContainers []string
        ShowLogsUntil             DeployCondition

        SkipEvents bool
}

Multitracker introduces fail-modes: IgnoreAndContinueDeployProcess, FailWholeDeployProcessImmediately and HopeUntilEndOfDeployProcess. Fail mode can be configured per-resource to completely ignore resource errors or ignore errors till all of the tracked resources become ready.

Only ResourceName and Namespace are required fields of MultitrackSpec.

Multitrack cli

There is minimal viable support of multitracker in kubedog cli. To use multitracker user must pass to kubedog stdin json structure which resembles golang structure MultitrackSpecs, for example:

cat << EOF | kubedog multitrack
{
  "StatefulSets": [
    {
      "ResourceName": "mysts1",
      "Namespace": "myns"
    }
  ],
  "Deployments": [
    {
      "ResourceName": "mydeploy22",
      "Namespace": "myns"
    }
  ]
}
EOF

Deprecation of rollout and follow trackers

BRIEF: users of rollout tracker should migrate to multitracker, users of follow tracker can continue using follow tracker.

Old trackers will remain in the source code and cli. But these trackers will not receive future support. The reason is: multitracker solves main kubedog in the more common way.

NOTE: Multitracker for now does not have follow-mode, it only works in rollout-mode (e.g. tracks resources until resources are ready). If you need follow mode, you can use old follow tracker for now. In the future multitracker will be configurable to run in either rollout or follow mode (in the follow mode multitracker should print info forever).

Installation

Linux amd64

Darwin amd64

Windows amd64

SHA256SUMS

Kubedog v0.2.0

Features

• Multitrack to track multiple resources at once
• Container logs options
• Enable gcp plugin
• Pretty status report

Fixes

• Fixes of conditions of Deployment ready status
• Various small fixes

Installation

Linux amd64

Darwin amd64

Windows amd64

SHA256SUMS

Kubedog v0.1.0

Fixes

• rollout track for sts hangs in particular situations
  • support for partition: 0, no hang in this situation
  • support for automatic actions in case of OnDelete, no error
  • debug messages for sts are more clearer
  • final status works in debug mode
• sts additional complete condition: updateReplicas==currentReplicas
• set default timeout to 0 for rollout track
• allow using arbitrary kube-config when running in-cluster-mode (e.g. from inside Pod)

Features

• --kube-context and --kube-config flags
• Configurable display out and err streams

Installation

Linux amd64

Darwin amd64

Windows amd64

SHA256SUMS

Kubedog v0.1.0-alpha.2

Fix warning ERROR: logging before flag.Parse

Kubedog should initialize flag package.

Added kubedog verion command

Installation

Linux amd64

Darwin amd64