Skip to content

Robin client improvements #30

@miguelmdh

Description

@miguelmdh

Motivation

This issue proposes some improvements in the robin client of the operator. This improvements do not only affect to the client, the possible drawbacks in the rest code must be fully analized.

Analysis

This proposals must be analized, implemented and fully tested, specially with E2E tests.

Technical Solution

  1. Check status codes. Robin returns 200, 201 and 202 in different situations that can cause requeues. It also returns 409 for conflicts. Other status codes (such as 400, 404, 500, etc) should also be analyzed and treated.
  2. Handle connection refused
  3. Add timeouts and variabilize it
  4. TODO

Some of this actions are already implemeted, but shows errors in the operator logs that we can remove by a proper message.

Acceptance criteria

  • Status codes checked
  • Connection refused handled
  • Timeouts

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions